GCC 3.0.2: errno conflict.

[Alexandre Oliva]

On Dec 14, 2001, Joe Buck <jbuck@synopsys.COM> wrote:

> Right, errno is allowed to be a macro, but the code in question does not
> have an #include of <errno.h> or of <cerrno>.

Good point.  I had failed to consider this possibility.  It does
indicate a bug in the library, then.  But it may be a bug in libstdc++
or in glibc.  It appears that it shouldn't be leaking into the user
space before <cerrno> or <errno.h> are included.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me