From: Richard Peters (R.A.Peters_at_[hidden])
Date: 2002-01-18 04:23:38
Quoting from C++ Standard 22.214.171.124:
<...> 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.
So... it seems the warnings aren't bogus.
----- Original Message -----
From: "David Abrahams" <david.abrahams_at_[hidden]>
> could you turn off the last-line test for .jam files? Jam doesn't have a
> problem with them, and as we all know, bogus warnings are worse than none
> ----- Original Message -----
> From: "Beman Dawes" <bdawes_at_[hidden]>
> > First, thanks to John Maddock, Rich Lee, and Jeremy Siek for already
> > a huge number of tab problems.
> > We've still got a way to go, however. See below. The "tabs" indication
> > means the file has one or more tabs. A no-no because editors with tabs
> > differently mess up file display. The "last line" indication means the
> > file does not end with a newline. Bothersome because some compilers
> > on this condition.
> > Please take a few minutes to fix any files you are responsible for.
> > please set your editor to "use tabs instead of spaces". That's good
> > for anyone writing code which will be read by someone other than the
> > author.
> > --Beman
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk