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

Subject: Re: [PATCH] 2nd patch Re: [Jade/OpenJade] g++ 2.95 C++ portability problems
From: Matthias Clasen <clasen@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 17 Aug 1999 12:42:34 +0200
> 
> 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.

Yes.

> 
> 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.

I tried -frepo with an older egcs release at home last night, 
and it didn't work.

> 
> 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.

gcc compiles one file at a time. It complains because it sees two
instantiations of the same template in one file. Moving them to 
different files would avoid that, but it may well be that linking
still fails. I don't know


> 


-- 
Matthias Clasen, 
Tel. 0761/203-5606
Email: clasen@xxxxxxxxxxxxxxxxxxxxxxxxxx
Mathematisches Institut, Albert-Ludwigs-Universitaet Freiburg


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


Current Thread