What is the purpose of 'warning: no newline at end of file'?

What is the purpose of 'warning: no newline at end of file'?

[Neo Anderson]

I don't even think it's a problem. Why do I need (or better have) a line 
ending?

Re: What is the purpose of 'warning: no newline at end of file'?

[Jonathan Turkanis]

Neo Anderson wrote:
> I don't even think it's a problem. Why do I need (or better have) a line 
> ending?

The C++ standard says: If a source file that is not empty does not end in a 
newline character, or ends in a newline character immediately preceded by a 
backslash character, the behavior is undefined. (2.1/1)

Jonathan

Re: What is the purpose of 'warning: no newline at end of file'?

[corey taylor]

And that undefined behavior is in the form of that warning you've
posted.  This simply lets you know what behavior the gcc developers
inserted.

You need the newline in order to have c++ standards behavior assumed
instead of gcc behavior -- it's a portability issue really.

corey

On 7/6/05, Jonathan Turkanis <technews@kangaroologic.com> wrote:
> Neo Anderson wrote:
> > I don't even think it's a problem. Why do I need (or better have) a line
> > ending?
> 
> The C++ standard says: If a source file that is not empty does not end in a
> newline character, or ends in a newline character immediately preceded by a
> backslash character, the behavior is undefined. (2.1/1)
> 
> Jonathan
> 
>

Re: What is the purpose of 'warning: no newline at end of file'?

[Neo Anderson]

So, what is the purpose of this warning? What possible 'damages' does this 
warning protect against?


And, what is the 'the behavior'?

----Original Message Follows----
From: Jonathan Turkanis <technews@kangaroologic.com>
To: gcc-help@gcc.gnu.org
Subject: Re: What is the purpose of 'warning: no newline at end of file'?
Date: Wed, 06 Jul 2005 21:41:20 -0600

Neo Anderson wrote:
>I don't even think it's a problem. Why do I need (or better have) a line 
>ending?

The C++ standard says: If a source file that is not empty does not end in a 
newline character, or ends in a newline character immediately preceded by a 
backslash character, the behavior is undefined. (2.1/1)

Jonathan

Re: What is the purpose of 'warning: no newline at end of file'?

[Ian Lance Taylor]

"Neo Anderson" <neo_in_matrix@msn.com> writes:

> So, what is the purpose of this warning? What possible 'damages' does
> this warning protect against?

None.  Personally, I think the compiler should only issue this warning
with -pedantic.

> And, what is the 'the behavior'?

In this quote:

> > The C++ standard says: If a source file that is not empty does not end
> > in a newline character, or ends in a newline character immediately
> > preceded by a backslash character, the behavior is undefined. (2.1/1)

"the behavior" refers to the behavior of the compiler.  It means that
the standard does not specify how the compiler must behave when it
sees a non-empty file which does not end with a newline.

Ian

Re: What is the purpose of 'warning: no newline at end of file'?

[Jonathan Turkanis]

[Sorry Neo, I think I sent you personal email accidentally]

Neo Anderson wrote:

 > So, what is the purpose of this warning? What possible 'damages' does this 
warning protect against?


I believe this language was added to the standard because at the time some 
systems were not able to handle files properly if they didn't end in a newline. 
This wording made it possible to provide conforming C++ implementations for 
those platforms.

I'm not sure if there still are any such systems, but because the standard has 
given implementations to freedom to do whatever they want (that's what undefined 
behavior means) if you tell them to process a file not ending in a newline, be 
warned that if you try to compile your code on another system, the compiler may 
refuse. I know, for example, that Comeau in strict mode won't compile it. For 
that matter, neither will gcc with -pedantic-errors.

Jonathan

 > And, what is the 'the behavior'?
 >
 > ----Original Message Follows----
 > From: Jonathan Turkanis <technews@kangaroologic.com>
 > To: gcc-help@gcc.gnu.org
 > Subject: Re: What is the purpose of 'warning: no newline at end of file'?
 > Date: Wed, 06 Jul 2005 21:41:20 -0600
 >
 > Neo Anderson wrote:
 >
 >> I don't even think it's a problem. Why do I need (or better have) a line ending?
 >
 >
 >
 > The C++ standard says: If a source file that is not empty does not end in a 
newline character, or ends in a newline character immediately preceded by a 
backslash character, the behavior is undefined. (2.1/1)
 >
 > Jonathan
 >
 >
 >
 >

Re: What is the purpose of 'warning: no newline at end of file'?

[Neo Anderson]

Thanks, that makes things much clearer for me.

----Original Message Follows----
From: Jonathan Turkanis <technews@kangaroologic.com>
To: gcc-help@gcc.gnu.org
Subject: Re: What is the purpose of 'warning: no newline at end of file'?
Date: Wed, 06 Jul 2005 22:40:28 -0600

[Sorry Neo, I think I sent you personal email accidentally]

Neo Anderson wrote:

 > So, what is the purpose of this warning? What possible 'damages' does 
this warning protect against?


I believe this language was added to the standard because at the time some 
systems were not able to handle files properly if they didn't end in a 
newline. This wording made it possible to provide conforming C++ 
implementations for those platforms.

I'm not sure if there still are any such systems, but because the standard 
has given implementations to freedom to do whatever they want (that's what 
undefined behavior means) if you tell them to process a file not ending in a 
newline, be warned that if you try to compile your code on another system, 
the compiler may refuse. I know, for example, that Comeau in strict mode 
won't compile it. For that matter, neither will gcc with -pedantic-errors.

Jonathan

 > And, what is the 'the behavior'?
 >
 > ----Original Message Follows----
 > From: Jonathan Turkanis <technews@kangaroologic.com>
 > To: gcc-help@gcc.gnu.org
 > Subject: Re: What is the purpose of 'warning: no newline at end of file'?
 > Date: Wed, 06 Jul 2005 21:41:20 -0600
 >
 > Neo Anderson wrote:
 >
 >> I don't even think it's a problem. Why do I need (or better have) a line 
ending?
 >
 >
 >
 > The C++ standard says: If a source file that is not empty does not end in 
a newline character, or ends in a newline character immediately preceded by 
a backslash character, the behavior is undefined. (2.1/1)
 >
 > Jonathan
 >
 >
 >
 >

Re: What is the purpose of 'warning: no newline at end of file'?

[Eljay Love-Jensen]

Hi Neo,

--- Foo.h ---
#ifndef Foo_H_ONCE
#define Foo_H_ONCE
extern int MyFoo;
#endif // Foo_H_ONCE<NO-NEWLINE>
--- --- ---

The "<NO-NEWLINE>" is a meta to indicate that there is no newline at the end of the file.

--- Foo.cpp ---
#include "Foo.h"
#include "Bar.h"
...yada yada yada...
--- --- ---

Is Bar.h supposed to be included?  Or is the comment-to-end-of-line at the end of Foo.h supposed to comment it out?

The behavior is undefined.

HTH,
--Eljay

Re: What is the purpose of 'warning: no newline at end of file'?

[Neo Anderson]

#include "Foo.h"

There is already a newline after it. What does the Standard say?

----Original Message Follows----
From: Eljay Love-Jensen <eljay@adobe.com>
To: Neo Anderson <neo_in_matrix@msn.com>, gcc-help@gcc.gnu.org
Subject: Re: What is the purpose of 'warning: no newline at end of  file'?
Date: Thu, 07 Jul 2005 06:38:09 -0500

Hi Neo,

--- Foo.h ---
#ifndef Foo_H_ONCE
#define Foo_H_ONCE
extern int MyFoo;
#endif // Foo_H_ONCE<NO-NEWLINE>
--- --- ---

The "<NO-NEWLINE>" is a meta to indicate that there is no newline at the end 
of the file.

--- Foo.cpp ---
#include "Foo.h"
#include "Bar.h"
...yada yada yada...
--- --- ---

Is Bar.h supposed to be included?  Or is the comment-to-end-of-line at the 
end of Foo.h supposed to comment it out?

The behavior is undefined.

HTH,
--Eljay

Re: What is the purpose of 'warning: no newline at end of file'?

[Eljay Love-Jensen]

Hi Neo,

>#include "Foo.h"

>There is already a newline after it. What does the Standard say?

The standard says that if you do not put in a newline at the end of Foo.h, the behavior is undefined.

The preprocessor directive #include "Foo.h" *includes* the newline at end-of-line.

No preprocessor that I know of puts in EXTRA newlines when it expands the preprocessor directives.  Putting in an EXTRA newline when the included file lacks one at the end-of-file is compiler specific (enhancement to standard) behavior.

Sincerely,
--Eljay