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: gcc-in-cxx update

From: Ian Lance Taylor <iant at google dot com>
To: Manuel LÃpez-IbÃÃez <lopezibanez at gmail dot com>
Cc: Sebastian Redl <sebastian dot redl at getdesigned dot at>, gcc at gcc dot gnu dot org
Date: Wed, 29 Apr 2009 07:54:20 -0700
Subject: Re: gcc-in-cxx update
References: <m3hc0729jr.fsf@google.com> <Pine.LNX.4.64.0904291120200.23778@digraph.polyomino.org.uk> <6c33472e0904290513j44b3cafdl77b38de0cd2619cd@mail.gmail.com> <Pine.LNX.4.64.0904291321570.25453@digraph.polyomino.org.uk> <49F859CB.5000508@getdesigned.at> <6c33472e0904290653g7297b4gd9860a5893c83280@mail.gmail.com>

Manuel LÃpez-IbÃÃez <lopezibanez@gmail.com> writes:

> 2009/4/29 Sebastian Redl <sebastian.redl@getdesigned.at>:
>> So MSC will warn about this construct, but GCC will not, due to its
>> whitespace rule:
>
> I think we should just remove the whitespace rule and implement the
> warning in C.

Actually it appears that the whitespace rule was already removed from
the C++ frontend in PR 36478.  So this may be a non-issue for
gcc-in-cxx.

Ian

References:
- gcc-in-cxx update
  - From: Ian Lance Taylor
- Re: gcc-in-cxx update
  - From: Joseph S. Myers
- Re: gcc-in-cxx update
  - From: Manuel López-Ibáñez
- Re: gcc-in-cxx update
  - From: Joseph S. Myers
- Re: gcc-in-cxx update
  - From: Sebastian Redl
- Re: gcc-in-cxx update
  - From: Manuel López-Ibáñez

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