MICO: Re: STL problem compiling MICO-2.2.1 with egcs-2.92.16 (19981019)

Jeffrey A Law law@cygnus.com
Mon Nov 2 01:34:00 GMT 1998


  In message < Pine.BSF.4.05.9811011307041.28793-100000@thelab.hub.org >you write:

  > How does submitting a bug to the egcs guys help, if we don't know that it
  > isn't a problem with MICO itself? :(
Somebody will look at the code that you send to determine if it's valid C++.

Just because C++ code works with an older compiler does not mean it is correct.

  > Generally, IMHO, when debugging a problem, you eliminate the source code
  > that you are trying to compile before you eliminate the compiler itself.
  > Since MICO 2.2.1 compiles fine for everyone using egcs 1.1, its pretty
  > safe to assume that its a problem with egcs-snapshot, but its not a
  > definite...
No, that is not safe to assume.  G++'s implementation is getting closer and
closer to the ANSI/ISO C++ standard.  As that happens, old non-conforming code
will stop compiling and will need to be fixed.

Nobody can tell for sure if it's a G++ bug or a bug in MICO until they see
the code.

jeff



More information about the Gcc-bugs mailing list