Path: utzoo!utgpu!attcan!ncrcan!hcr!jim
From: jim@hcr.UUCP (Jim Sullivan)
Newsgroups: comp.unix.i386
Subject: Re: how about RN and Interactive?
Message-ID: <1921@hcr.UUCP>
Date: 31 Aug 89 13:32:09 GMT
References: <2071@kodak.UUCP>
Reply-To: jim@hcrvax.UUCP (Jim Sullivan)
Organization: HCR Corporation, Toronto
Lines: 43

In article <2071@kodak.UUCP> mark@kodak.UUCP () writes:
>Not liking readnews, we wanted to compile the rn package.  I can tell you that
>there were lots of problems. We were able to fix most of them but the following
>error has us stimied:
>
>
>ngdata.c: 132: extra tokens (ignored) after directive
>ngdata.c: 141: extra tokens (ignored) after directive
>ngdata.c: 168: extra tokens (ignored) after directive
>ngdata.c: 177: extra tokens (ignored) after directive

This message is produced when the pre-processor encounters a directive with
extra tokens at the end (oh, really? :-).  This is the result of a change in
the pre-processor from previous releases.

In previous releases of the pre-processor, the construct:

#ifdef i386
code
code
code
#endif i386

was legal.  The offending line in the current pre-processor is the "#endif i386"
line.  "i386" is considered a token and the "#endif" directive does not take
and extra tokens so the error message gets printed.  I guess that someone in
ANSI though that extra tokens were evil and should be removed (I agree
actually).  The construct is often used in large programs with many #ifdefs
to indicate where an #ifdef for a particular #define ends. The correct form is:

#endif /* i386 */

So you can ignore the extra token messages or write a awk script to change
them into legal #endif statements (this exercise is left to the user)

>"ngdata.c", line 187: syntax error
>"ngdata.c", line 194: dirp undefined
>"ngdata.c", line 197: warning: illegal pointer/integer combination, op =
>

I think that this is a syntax error :-)

Jim Sullivan