Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: rlerallut at free dot fr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40474
--- Comment #1 from rlerallut at free dot fr 2009-06-17 11:41 ---
Created an attachment (id=18011)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18011&action=view)
Trivial program that does *not* end with a newline
Make sure that your editor does not add silently a
--- Comment #3 from rlerallut at free dot fr 2009-06-17 13:51 ---
(In reply to comment #2)
> This is deliberate; see bug 14331.
Err... What happened to following the standard ?
"
If a source file that is not empty
does not end in a new-line character, or ends in a
--- Comment #5 from rlerallut at free dot fr 2009-06-17 14:15 ---
(In reply to comment #4)
> Behavior being undefined means no requirement for a diagnostic, and the
> phase 1 mapping can introduce this newline in any case.
Allright, so if I develop my code with gcc 4.3, I have
--- Comment #8 from rlerallut at free dot fr 2009-06-18 18:04 ---
(In reply to comment #7)
> The warning was removed on purpose per user request, so this is WONTFIX.
Keeping an once of compatibility (or adding an option) between two minor
versions would have been appreciated. O
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: rlerallut at free dot fr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43820
--- Comment #8 from rlerallut at free dot fr 2010-04-20 18:41 ---
@Chris Jefferson : indeed, if I roll my own "auto_ptr" locally, I get the
proper warning, as well as if I use -Wsystem-headers (didn't know that one).
@Paolo Carlini : I'm using the default standard
--- Comment #11 from rlerallut at free dot fr 2010-04-20 19:09 ---
I don't think auto_ptr is special and I, as a mere user, would appreciate you
didn't hide *helpful* warnings from anywhere (but I do also appreciate your
efforts in limiting spurious warnings !).
I have the