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: error: "no newline at end of file"

From: Robert Dewar <dewar at adacore dot com>
To: Zack Weinberg <zackw at panix dot com>
Cc: Martin Michlmayr <tbm at cyrius dot com>, GCC Development <gcc at gcc dot gnu dot org>
Date: Sun, 01 Apr 2007 18:43:33 -0400
Subject: Re: error: "no newline at end of file"
References: <eb97335b0704010830q34a14df1qc7d2ffd447827631@mail.gmail.com> <20070401214157.GF913@deprecation.cyrius.com> <eb97335b0704011454t411be5ddnfcb2ab157c5a2dec@mail.gmail.com>

Zack Weinberg wrote:

Ugh.  That puts us in the position of having to decide whether command
line definitions "count" as previous definitions for 6.10.3p3.  I'm
inclined to think that they do, or rather, that saying they don't
involves more bending of the language than I am comfortable with.  I
could be convinced otherwise.


It's not bending the language, the standard has nothing whatever to say
about -D. I see no reason not to be completely permissive wrt -D if it
is going to make transition smoother.

Follow-Ups:
- Re: error: "no newline at end of file"
  - From: Zack Weinberg

References:
- Re: error: "no newline at end of file"
  - From: Zack Weinberg
- Re: error: "no newline at end of file"
  - From: Martin Michlmayr
- Re: error: "no newline at end of file"
  - From: Zack Weinberg

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