On Thu, 14 Feb 2002 [EMAIL PROTECTED] wrote:

> >how big it is,
>
> Quite, around 20 subprojects that compile into binaries, of varying size.

kilo lines of code?

> > if it has strict standards conformance
>
> Need posix, the rest we implement ourselves.

i meant whether your code relies on gcc'isms, like __attribute__ or
'inline',whether it relies on undefined gcc behaviour (which the kernel
occasionally does), whether you use the std namespace correctly and
give functions throw specifications, etc.

> >in general, gcc3 is much more conforming to the c++ standard,
>
> How? FM to RT... :-)

http://gcc.gnu.org, in particular
http://gcc.gnu.org/onlinedocs/gcc-3.0.3/gcc_2.html#SEC2 and
http://gcc.gnu.org/faq.html#multiple

> >basically, upgrading the compiler is no big deal, and several compilers
> >can co-exist peacefully
>
> That means simply a binary of gcc and a binary of gcc3, Right? Or duplicate
> sets of system includes, libraries and the like?

duplicate set of binaries and compiler headers, but not system headers.
stuff like the std c++ library tends to change with each compiler
version, for example.

> Sounds tempting if it's something simple. Prob is we have >10 developers
> working on this system, I don't want to go into time overhead due to
> compiler compatibility issues, that'll cause us to waste half a week
> figuring out why half the code won't compile.. ;-)

try it and see. if you have a reasonable build process, it shouldnt take
more than a few hours or one dayto install the new compiler (be it
2.95.2 or 3.x)  and assess the amount of work required to support it.
--
mulix

http://vipe.technion.ac.il/~mulix/
http://syscalltrack.sf.net/



=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Reply via email to