Re: EOF location?
- From: Clever Monkey <clvrmnky.invalid@xxxxxxxxxxxxxxxxxxx>
- Date: Tue, 30 May 2006 11:04:58 -0400
Richard wrote:
I carefully noted in the rest of my reply that this is an API convention. I never suggested that the EOF char had to be unique, but the very tools that were used upthread would, in fact, never allow one to "see" the EOF. They use APIs that look for it and consume it.A single 0x1A (control-Z in ASCII) is used to indicate EOF,
That is only true if the particular program tests specifically for that
character. Any file can have Ctrl-Zs scattered through them and what
happens is entirely dependent on the program.
[...]
Except for stdin and friends, which are files (or have file semantics) on POSIX systems. Since there is no special character marking EOF on most POSIX systems they are not equivalent. But the chars are used similarly in other regards.similar to EOT in POSIX environments.
Except that EOT is 'End of Transmission' and has no effect of files.
.
- Follow-Ups:
- Re: EOF location?
- From: Richard
- Re: EOF location?
- References:
- EOF location?
- From: HeyBub
- Re: EOF location?
- From: Pete Dashwood
- Re: EOF location?
- From: Clever Monkey
- Re: EOF location?
- From: Richard
- EOF location?
- Prev by Date: Re: PIC P put to real use
- Next by Date: Re: PIC P put to real use
- Previous by thread: Re: EOF location?
- Next by thread: Re: EOF location?
- Index(es):
Relevant Pages
|