This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC 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: Extension compatibility policy

From: Robert Dewar <dewar at adacore dot com>
To: Giovanni Bajo <giovannibajo at libero dot it>
Cc: Marc Espie <espie at quatramaran dot ens dot fr>, gcc at gcc dot gnu dot org
Date: Mon, 28 Feb 2005 09:24:20 -0500
Subject: Re: Extension compatibility policy
References: <pan.2005.02.26.19.57.52.648712@navi.cx> <20050227140225.296C71C6@quatramaran.ens.fr> <038101c51d87$3ed11f10$d4b02997@bagio>

Giovanni Bajo wrote:

Marc Espie <espie@quatramaran.ens.fr> wrote:

Personally, I would even say that it would be *great* if gcc would
start warning if you use any extension, unless you explicitly disable
those warnings... (except for __extension__ in header files, and then
I've stumbled upon situations where it hurts still).


That is *exactly* what -pedantic is meant to be. If it does not, patches are
welcome.


Not quite, Marc is suggesting that -pedantic be the default if I read
the above statement correctly.

Follow-Ups:
- Re: Extension compatibility policy
  - From: Marc Espie

References:
- Extension compatibility policy
  - From: Mike Hearn
- Re: Extension compatibility policy
  - From: Marc Espie
- Re: Extension compatibility policy
  - From: Giovanni Bajo

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