eric@nosun.west.sun.com (Eric Hanchrow) (01/20/90)
gcc version 1.36
Here's one input file (call it `little.c'):
----------------------------------------------------------------
#include <stdio.h>
void
main(void)
{
}
----------------------------------------------------------------
Perhaps you can't tell by looking, but each line in that file ends in
a carriage-return/line-feed pair (like a DOS file).
Command line: gcc little.c -o little
tm.h: linked to ./config/tm-sparc.h
md: linked to ./config/sparc.md
Machine: SparcStation 1
OS: SunOS 4.0.3c
What seems to be wrong:
little.c:1: #include expects "fname" or <fname>
Now, perhaps you're saying, ``What did you expect -- the ANSI standard
doesn't define the carriage-return character as whitespace!!''
(Actually, the only reference I have is Kernighan & Ritchie 2nd ed.,
and they're not precise about what constitutes whitespace). If so,
then why does the same file, except without the `#include' line,
compile without a peep? Seems to me that either carriage-return is
whitespace, in which case both files should compile silently, or it
isn't, in which both should fail.
Of course, as usual, the other possiblilty is that I'm hopelessly
confused, but then, you're always free to ignore these bug reports.
Thanks!!!
-------------------------------------------------------------------------
|Eric Hanchrow yamada-sun!eric@nosun.west.sun.com |
|Phase III Logic, Inc. ...!{tektronix, sun}!nosun!yamada-sun!eric |
|1600 N.W. 167th Place Beaverton, OR 97006 |
|Voice: (503)-645-0313 Fax: (503)-645-0207 as of 13-Dec-89 |
-------------------------------------------------------------------------