[kde-discuss] #include with no newlines & strange effects

[Paul Floyd]

> then add a newline to the end of t.c and try that again. Question: is that
> correct behavior?

Hi

Yes, this is 100% correct behaviour. 5.1.1.2 of ISO/IEC 9899, para 1, numbered
phase 2 says "A source file that is not empty shall end in a new-line character,
which shall not be immediately preceded by a backslash character". I don't have
the C++ standard or anything older for C at hand, but I expect that they say the
same thing.

The source needs fixing.

A+
Paul