Re: [g++] namespace problem

[Martin Sebor <sebor at roguewave dot com>]

brent verner wrote:
> 
> On 01 Sep 2000 at 03:22 (-0400), brent verner wrote:
> | Hi,
> |
> |   I'm working on the C compatibility headers for libstdc++-v3
> | (process detailed: http://www.cantrip.org/cheaders.html). There appears
> | to be a buglet floating around somewhere in the compiler system that
> | (,I believe, wrongly) finds ambiguity with function calls defined
> | in separate namespaces.
> 
> ...er, bug in the Brent-system. adding -fno-builtin fixes the problem...
> shoulda RTFM sooner :).
> 
> Question: other than specifying -fno-builtin, is there any way to
>           tell the compiler to _not_ use _specific_ builtins? (just
>           curious)

Wrt. to the this project (just a different implementation), is there a
way to prevent the warning: ANSI C does not allow `#include_next' and
still use the directive? gcc somehow knows not to give the warning for
its own or the OS headers (on Linux) but it complains about it in my own
<limits.h> (using a full pathname doesn't work).

Thanks
Martin

> 
> thanks.
>   Brent
> 
> --
> Damon Brent Verner                        o      _     _         _
> Cracker JackŪ Surprise Certified  _o     /\_   _ \\o  (_)\__/o  (_)
> brent@rcfile.org                _< \_   _>(_) (_)/<_    \_| \   _|/' \/
> brent@linux1.org               (_)>(_) (_)        (_)   (_)    (_)'  _\o_