This is the mail archive of the
mailing list for the GCC project.
Re: Switching to C++ by default in 4.8
- From: Dave Korn <dave dot korn dot cygwin at gmail dot com>
- To: Eric Botcazou <ebotcazou at adacore dot com>
- Cc: Torvald Riegel <triegel at redhat dot com>, gcc at gcc dot gnu dot org, Michael Matz <matz at suse dot de>, Xinliang David Li <davidxl at google dot com>, Jakub Jelinek <jakub at redhat dot com>, Richard Guenther <richard dot guenther at gmail dot com>, Bernd Schmidt <bernds at codesourcery dot com>, Gabriel Dos Reis <gdr at integrable-solutions dot net>, David Edelsohn <dje dot gcc at gmail dot com>, Diego Novillo <dnovillo at google dot com>
- Date: Sat, 14 Apr 2012 00:33:18 +0100
- Subject: Re: Switching to C++ by default in 4.8
- References: <4F7B356E.firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com>
On 11/04/2012 22:13, Eric Botcazou wrote:
>> So, you only know it's 2 tokens once you know all of tree.def? I'm
>> aware that this is just some arbitrary example, but I believe this
>> actually strengthens the concern I had.
> Well, if you don't know of FIELD_DECL, you won't go very far, really.
But still, wouldn't it be nice and enhance clarity to be able to use a
different character/token between GET and FIELD_DECL than between FIELD and DECL?
(Anyway, I still think we should start by just redefining GET_FIELD_DECL et.
al. as C++ inline functions - or macros that invoke C++ inline functions, or
whatever else that works better for whatever reason, regardless of the
implementation details - and let the existing code continue to use them in
exactly the same way as before.)