This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [C++] deprecate overload resolution extension?
- To: Jason Merrill <jason at redhat dot com>
- Subject: Re: [C++] deprecate overload resolution extension?
- From: Nathan Sidwell <nathan at codesourcery dot com>
- Date: Wed, 28 Feb 2001 09:18:41 +0000
- CC: dewar at gnat dot com, mark at codesourcery dot com, gcc at gcc dot gnu dot org
- Organization: Codesourcery LLC
- References: <20010227235254.E99B2F28A8@nile.gnat.com> <u94rxfk6x0.fsf@casey.cambridge.redhat.com>
Jason Merrill wrote:
> We will be forcing the disambiguation; in the C++ frontend, pedwarns are
> errors by default. But I would like people to be able to build code that
> relies on this with -fpermissive; again, I put this extension in because
> things were breaking without it (though I don't remember what).
Making it permissive is fine by me, but ...
What is the intended difference between deprecated things and permissive
things?
* deprecated features are warned[1] and that inhibited with -fdeprecated
* permissive features are errored and that can be warned with -fpermissive
* deprecated features will be removed 'in some future release'
Are we also intending to support permissive features forever?
nathan
[1] Given the robust treatment of permissive, I'm mildly surprised that
deprecated is a warning -- in my experience users tend to ignore those.
--
Dr Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery LLC
'But that's a lie.' - 'Yes it is. What's your point?'
nathan@codesourcery.com : http://www.cs.bris.ac.uk/~nathan/ : nathan@acm.org