delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | ieva01.lanet.lv: pavenis owned process doing -bs |
Date: | Tue, 24 Aug 1999 09:47:35 +0300 (WET) |
From: | Andris Pavenis <pavenis AT lanet DOT lv> |
To: | George Ryot <ryot AT bigfoot DOT com> |
cc: | djgpp AT delorie DOT com |
Subject: | Re: c++ const definition in djgpp 2.95 problem |
In-Reply-To: | <37c1c55c.147383@news.clara.net> |
Message-ID: | <Pine.A41.4.05.9908240944250.45582-100000@ieva01.lanet.lv> |
MIME-Version: | 1.0 |
Reply-To: | djgpp AT delorie DOT com |
X-Mailing-List: | djgpp AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
On Mon, 23 Aug 1999, George Ryot wrote: > GCC 2.8.1 would allow many non-ansi things, it still does but the > default behaviour has changed. With 2.8.1 the -pedantic switch is > required (or -Wall which implies -pedantic) to get these warnings > issued. With 2.9.5 the default appears to be -pedantic-errors, and True. It's -pedantic-errors by default now (see gcc info file). However You can use new option -fpermissive that makes gcc behave like it did before (almost) > -Wall no longer implies -pedantic. So now you get errors when before > you maybe didn't even get a warning. If you use -pedantic with 2.9.5 > the errors are downgraded to warnings so it should work just like > 2.8.1. > gcc-2.95.x doesn't assume -pedantic-errors if You use one of -fpermissive or -fpedantic. Andris
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |