Date: Fri, 6 Sep 2002 22:29:24 -0400 Message-Id: <200209070229.g872TOl03706@envy.delorie.com> X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT delorie DOT com using -f From: DJ Delorie To: djgpp AT delorie DOT com In-reply-to: <001f01c25614$e8cd52a0$2ca0c6d4@noos.fr> (aubourg@paris.ensmp.fr) Subject: Re: No new line at end of file? References: <3d71a27d DOT 23705885 AT news DOT nzwide DOT ihug DOT co DOT nz> <3d746b3c DOT 3046168 AT news DOT nzwide DOT ihug DOT co DOT nz> <3d795645$0$24320$79c14f64 AT nan-newsreader-02 DOT noos DOT net> <200209070134 DOT g871YGP03030 AT envy DOT delorie DOT com> <001f01c25614$e8cd52a0$2ca0c6d4 AT noos DOT fr> Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > As I see it, one very important function of --ansi is to disable specific > gcc enhancements. Getting rid of the newline requirement sounds like an > enhancement to me. Furthermore, it ensures backward compatibility. No, --ansi is there to get rid of gcc-specific features that *conflict* with the ANSI standard. It's not an excuse to add random incompatibilities otherwise. > I suppose this is a decision beyond djgpp itself tho. Right. DJGPP just ports gcc.