This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug preprocessor/27750] bogus 'backslash-newline at end of file' warning
- From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 24 May 2006 06:33:16 -0000
- Subject: [Bug preprocessor/27750] bogus 'backslash-newline at end of file' warning
- References: <bug-27750-6809@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #5 from pinskia at gcc dot gnu dot org 2006-05-24 06:33 -------
(In reply to comment #4)
> > This might be why it is undefined at compile time if the file does not end in a
> > new-line or not :).
>
> However, GCC *does* supports this as an extension, hence the expected pedwarn.
It is not really an extension, just undefined at compile time which is
diffferent than supporting.
>
> > I don't think that warning is that bogus. It is true too.
>
> Huh? The backslash-newline occur in the middle of a comment, not at the end of
> a file.
so ... The standard requires that to be an backslash-newline even without the
comment there.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27750