public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Paul Lim" <paullimjh@hotmail.com>
To: zack@codesourcery.com, dewar@gnat.com
Cc: jsturm@one-point.com, gcc-help@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: Help : File does not end with newline
Date: Sun, 30 Sep 2001 17:44:00 -0000	[thread overview]
Message-ID: <F229CdclVXOK7S8MyBu0000ea90@hotmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2177 bytes --]

Hi to all,

Zack, I have attached my file here for you to check. I have verified that 
the file attached to you does not compile cleanly i.e it has the "File does 
not end with newline" warning.

I have followed the method recommended by Jeff. I opened up my .h file under 
Unix vi and saved it again. It then managed to compile cleanly without any 
error.

For your information and necessary action.

Thank you once again for all your advise.

Sincerely
Paul

>From: Zack Weinberg <zack@codesourcery.com>
>To: dewar@gnat.com
>CC: jsturm@one-point.com, paullimjh@hotmail.com, gcc-help@gcc.gnu.org, 
>gcc@gcc.gnu.org
>Subject: Re: Help : File does not end with newline
>Date: Sun, 30 Sep 2001 14:43:43 -0700
>
>On Sun, Sep 30, 2001 at 12:58:42PM -0400, dewar@gnat.com wrote:
> > <<Not directly.  But Windows does seem to have a plethora of broken 
>editor
> > software.  Try to open/save this file in another source code editor, 
>such
> > as emacs or even Windows Notepad.
> > >>
> >
> > Note that it is entirely within normal Windows standards for the last
> > character in the file to be 0x1A, you can even argue that this is the
> > standard format, so many editors in Windows put this character there,
> > but typical Unix software is not setup to properly handle this end
> > of file character on Windows, so perhaps that is the problem.
>
>If this turns out to be the problem, I am willing to add code to
>cpplib to recognize 0d 0a 1a EOF as a proper end of file.  Before
>doing that, though, I would like to see the complete error log
>reported by the compiler.  "warning: no newline at end of file" is not
>a fatal error; if that was the only problem reported, compilation
>would have succeeded.  There must have been at least one more error
>message.  (If the problem is a trailing 0x1a, gcc should have printed
>"stray '\32' in program").
>
>I would also like to see the complete contents of diary.h, in a format
>guaranteed to preserve control characters (for instance, gzipped and
>then MIME-attached or uuencoded).
>
>zw


_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp

[-- Attachment #2: Paul.zip --]
[-- Type: application/zip, Size: 7352 bytes --]

             reply	other threads:[~2001-09-30 17:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-30 17:44 Paul Lim [this message]
2001-09-30 18:21 ` Zack Weinberg
  -- strict thread matches above, loose matches on Subject: below --
2001-09-30 10:02 dewar
2001-09-30 14:47 ` Zack Weinberg
2001-09-30  9:26 Paul Lim
2001-09-30  9:44 ` Jeff Sturm

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=F229CdclVXOK7S8MyBu0000ea90@hotmail.com \
    --to=paullimjh@hotmail.com \
    --cc=dewar@gnat.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=jsturm@one-point.com \
    --cc=zack@codesourcery.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).