This is the mail archive of the gcc-help@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: preprocessing directive with no new-line character

From: Toebs Douglass <toby at winterflaw dot net>
To: gcc-help at gcc dot gnu dot org
Date: Mon, 17 Jul 2017 19:41:04 +0200
Subject: Re: preprocessing directive with no new-line character
Authentication-results: sourceware.org; auth=none
References: <20170717131958.GA23989@zira.vinc17.org> <CA+7wUswGQyztN70aiHRp1RARa4-erV6cYN2Ys=gD0st6x-Z4PA@mail.gmail.com> <20170717141517.GA29555@zira.vinc17.org> <8cb25e84-cac2-4185-81e1-bbc3f14d653c@gmail.com>

On 17/07/17 17:45, Martin Sebor wrote:
> I agree.  C requires non-empty source files to end in an unescaped
> new-line character.

I was thinking this too, but I thought - the compilation unit as seen by
the compiler will be correct, for there is a trailing newline once the
pre-processor directive has been removed by the pre-processor.

But I don't know how these things really work - it's just a
not-obviously-wrong line of thought.

References:
- preprocessing directive with no new-line character
  - From: Vincent Lefevre
- Re: preprocessing directive with no new-line character
  - From: Mathieu Malaterre
- Re: preprocessing directive with no new-line character
  - From: Vincent Lefevre
- Re: preprocessing directive with no new-line character
  - From: Martin Sebor

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