This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


Zack Weinberg <zack@codesourcery.com> writes:

| On Thu, May 23, 2002 at 04:56:47PM +0200, Gabriel Dos Reis wrote:
| > Zack Weinberg <zack@codesourcery.com> writes:
| > 
| > | On Thu, May 23, 2002 at 07:41:13AM +0200, Gabriel Dos Reis wrote:
| > | > 
| > | > You're missing the entire point.  The proposal is this:  A flag
| > | > --no-standard-headers maintains the actual (non-comforming)
| > | > behaviour.  When turned off it delivers the expected (== standard)
| > | > semantics.  As such existing programs abusing of that non-conforming
| > | > behaviour have the old semantics when turned on.  Nothing breaks.
| > | 
| > | If the flag is off by default, all the old programs do indeed break.
| > 
| > Not all old programs. Only those programs that happen to depend
| > (intentionally?) on a non-standard semantics.  It doesn't serve
| > purposes to exagerate things to the extreme.
| 
| I never said that all old programs would break.  I said that all
| programs that depend intentionally on existing semantics would break,
| that there are lots of them out there, and that fixing some of them
| (such as Xfree86) would be nontrivial.

Oh wait, could you name the standard header that XFree86 replaces and
on which systems?

-- Gaby


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]