Re: [PATCH] 2nd patch Re: [Jade/OpenJade] g++ 2.95 C++ portability problems

[Adam Di Carlo <adam@xxxxxxxxxxx>]

Matthias Clasen <clasen@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> writes:

> It seems to work for CVS OpenJade as well (I can't say for sure, since
> I first had to install gcc-2.95 and now it is still compiling, but
> it already build libsp successfully).
> 
> But the patch fails if unsigned int != size_t, doesn't it ?

Well, compilation would probably fail, I guess.

Furthermore, if you think about it, whether unsigned int is the same
as size_t or not is really not a GCC issue either.  Which is another
reason why my patch is rather broken.

I just question whether we should be using -fno-implicit-templates or
-frepo or maybe some other system.  It just doesn't seem that the way
C++ template instantiation happens is handled all that cleanly
currently.

Have you read and understood the gcc 2.95 info pages on Template
Instantiation?  I read that but don't quite understand it...

> The CVS version of OpenJade needs more fixes for gcc-2.95 anyway. 
> Here is another untested idea: Wouldn't it be enough to move the
> potential duplicates to different files to avoid the conflict ?

Not sure quite what you mean.

--
.....Adam Di Carlo....adam@xxxxxxxxxxxxxxxx<URL:http://www.onShore.com/>


 DSSSList info and archive:  http://www.mulberrytech.com/dsssl/dssslist