🚀 go-pugleaf

A null in a file (indicated by ^@ below) is interpreted by gcc 1.27 as
an end-of-file on both Unix and VAX VMS (we found a null in types.h in
the recent VMS gcc distribution):
 
404 plot79>cat foo.c
#include <stdio.h>

main()
{
        printf("hello,world\n");
}

Sun OS 4.0 cc flags it as an error:

405 plot79>cc -o foo foo.c
"foo.c", line 2: illegal character: 000 (octal)

gcc 1.27 just quits after the NUL; using -E or -S verifies that.

406 plot79>gcc -o foo foo.c
ld: Undefined symbol 
   _main 

My personal preference would be for NUL to be simply ignored; otherwise,
an error should be generated.  End-of-file should not be, I think.
-------