Warning: no newline at end of file

su*********@gmail.com wrote:

hi,
I am using gcc 3.4.4 for c++, i am getting the following
warning if there is no new line at the EOF. Why this warning and i am
not getting the warning in vc++ compiler.

gcc expects a new line at the end of a file, give it one.

Ian

<su*********@gmail.com> wrote in message
news:11**********************@g47g2000cwa.googlegr oups.com...

hi,
I am using gcc 3.4.4 for c++, i am getting the following
warning if there is no new line at the EOF. Why this warning and i am
not getting the warning in vc++ compiler.

thanks,
suri

Because gcc wants the newline and vc++ doesn't care.

no, ,just vc do not issue this warning.

however, there should be a potential problem if we miss newline...

"baibaichen" <ba********@gmail.com> wrote in message
news:11*********************@g14g2000cwa.googlegro ups.com...

no, ,just vc do not issue this warning.

however, there should be a potential problem if we miss newline...

I don't see how there could possibly be a problem if VC handles it.

Jim Langston wrote:

"baibaichen" <ba********@gmail.com> wrote in message
news:11*********************@g14g2000cwa.googlegro ups.com...

no, ,just vc do not issue this warning.

however, there should be a potential problem if we miss newline...

I don't see how there could possibly be a problem if VC handles it.

http://gcc.gnu.org/ml/gcc/2001-07/msg01120.html

Arne

--
[--- PGP key FD05BED7 --- http://www.root42.de/ ---]

"Arne Schmitz" <ar**********@gmx.net> wrote in message
news:42*************@news.dfncis.de...

Jim Langston wrote:

"baibaichen" <ba********@gmail.com> wrote in message
news:11*********************@g14g2000cwa.googlegro ups.com...

no, ,just vc do not issue this warning.

however, there should be a potential problem if we miss newline...

I don't see how there could possibly be a problem if VC handles it.

http://gcc.gnu.org/ml/gcc/2001-07/msg01120.html

Arne

I just tested that in msvc++ .net 2003 and it compiles without problem.

File iostreamtest.h:
#include <iostream>
(no newline at end)

File stringtest.h:
#include <string>
(no newline at end)

File main.cpp:
#include "iostreamtest.h"
#include "stringtest.h"
int main()
{
std::string test = "Hello";
std::cout << test;
std::string Wait;
std::cin >> Wait;
}

Compiles and outputs Hello

Again, the compiler handles that. It probably just includes an extra
newline for include files.

So, since the compiler handles there not being no newlines at the end of a
file, it doesn't seem to be an issue so doesn't need a warning.

Jim Langston wrote:

So, since the compiler handles there not being no newlines at the end of a
file, it doesn't seem to be an issue so doesn't need a warning.

*Your* compiler handles it.
Quoting http://www.cse.unsw.edu.au/~patrykz/...fc/tdfc9.html:

"The ISO C standard, section 5.1.1.2, states that source files must end with
new lines."

Arne

--
[--- PGP key FD05BED7 --- http://www.root42.de/ ---]

Arne Schmitz wrote:

Jim Langston wrote:

So, since the compiler handles there not being no newlines at the end of a
file, it doesn't seem to be an issue so doesn't need a warning.

*Your* compiler handles it.
Quoting http://www.cse.unsw.edu.au/~patrykz/...fc/tdfc9.html:

"The ISO C standard, section 5.1.1.2, states that source files must end with
new lines."

Arne

ISO C++ Standard.

2.1/1.2 "If a source file that is not empty does not end in a new-line
character, or ends in a new-line character immediately preceded by a
backslash character, the behavior is undefined".

Ergo, both compilers are performing within the spec. You could get a
working program. You could get a warning. You could get an error.
Your program could compile to a virus that would wipe out the Internet
as we know it. It's UB.