This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: error: "no newline at end of file"
Joe Buck <Joe.Buck@synopsys.COM> writes:
| On Tue, Mar 27, 2007 at 02:23:47PM +0100, Manuel López-Ibáñez wrote:
| > On 27/03/07, Martin Michlmayr <tbm@cyrius.com> wrote:
| > >* Manuel López-Ibáñez <lopezibanez@gmail.com> [2007-03-27 14:08]:
| > >> C++ preprocessor emits errors by default for nonconformant code,
| > >> following the C++ frot-end default behaviour. Users can use the
| > >> -fpermissive option to downgrade these diagnostics from errors to
| > >> warnings.
| > >
| > >s/frot-end/front-end/
| > >
| > >I'm not sure whether "nonconformant code" is specific enough. Apart
| > >from this, it looks good.
| >
| > It comes from the definition of fpermissive in invoke.texi.
|
| Users aren't going to know from this language what has changed. Manuel,
| since you're the guy who has been studying the warnings lately: which
| other preprocessor diagnostics, other than "no newline at end of file",
| are affected by this change?
I believe there is a bug in the diagnostic flag setting.
A pedwarn is a warning by default. It becomes a hard error only if
-pedantic. If that is not happening, then we have a bug.
-- Gaby