Re: [RFC] libstdc++/6720 and libstdc++/6671

[Phil Edwards <phil at jaj dot com>]

On Tue, May 21, 2002 at 11:12:45PM -0700, Zack Weinberg wrote:
>  If the ext/ header names can be made not to clash with
> the standard ones, well and good; if not, tell people not to use 
> -I $(prefix)/include/g++-3/ext and forget it.

We've done the latter already (earlier this week).

I am completely comfortable with requiring users to type

    #include <ext/whatever>

rather than <whatever> and fiddling with -I options.  The examples I
gave in a PR audit trail somewhere are <sys/types.h> and <X11/Xcrap.h>
and <net/if.h> and so forth.  Nobody writes "#include <types.h>" and then
specifies -I/usr/include/sys (and lives to tell about it).


> Note that the problem of <foo> including <bar> and getting <ext/bar>

How disgusting.  I hadn't even considered that possibility.


> can be dealt with by having foo use #include "bar", which puts the
> directory containing foo at the head of the search path.  (Unless the
> user provided -I-, but once again, if they did that they meant it.)

I think Paolo is right; this should be doable.



Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams