[1715] in Athena Bugs
hc
daemon@ATHENA.MIT.EDU (jfc@ATHENA.MIT.EDU)
Sat Jan 28 19:22:39 1989
From: <jfc@ATHENA.MIT.EDU>
To: bugs@ATHENA.MIT.EDU
Date: Sat, 28 Jan 89 19:22:21 EST
hc error/warning listings often look like this:
w "rul_def.c",L14/C52: redraw_edit:
| This function should be declared "extern". Assumed.
E "rul_def.c",L20/C26:
struct _tdef *, char *)'.
w "rul_def.c",L83/C7: '=' used where '==' may have been intended.
| You can eliminate this warning by explicitly including '!= 0'.
w "rul_def.c",L117/C8: '=' used where '==' may have been intended.
| You can eliminate this warning by explicitly including '!= 0'.
w "rul_def.c",L126/C10: '=' used where '==' may have been intended.
| You can eliminate this warning by explicitly including '!= 0'.
Object module not generated.
1 user error 8 warnings
MetaWare High C Compiler 1.4r 28-Jan-89 19:16:50 rul_def.c Page 1
| Type `void (*)()' is not assignment compatible with type `void (*)(
*** Exit 1
Stop.
Note that the first line of the error message along with the banner line
was printed at the end of the listing, not at the point of the error where
it belongs. I suspect it was directing some output to stdout instead of
stderr. (Output for this was redirected to a file, so buffering may not
be the same as normal terminal I/O.)
I used these options: -O -g -H+w -Hnocpp
--John Carr