This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: EOF character in parser
> I don't know if this is true or not. cpplib passes O_BINARY to open()
> on systems that define that constant, but the comments in cppfiles.c
> claim that this only disables translation of \r\n style line breaks.
O_BINARY disables *all* special handling of files. DJGPP itself
doesn't happen to put 0x1a in files, so it might just be a coincidence
that this hasn't been a problem yet.
And the comments don't say that that's all that O_BINARY does. It
just says that that's the reason it uses O_BINARY.
> There is no special handling of 0x1a in cpplib.
There should be, but it's probably not a big issue.