On Sat, Feb 17, 2001 at 04:50:25PM -0500, Jeff Trawick wrote:
> Ben Laurie <[EMAIL PROTECTED]> writes:
>
> > But the caller typically _does_ care if its EOF,
>
> if you're talking about filters, I would contend that the caller
> typically cares about eos, not EOF
>
> eos is the bucket brigade equivalent to EOF in traditional file
> reading
>
> an EOF condition on the underlying read operation of a particular
> bucket may or may not mean that it is the end of the brigade for the
> filter to process
Right. But I'm with Ben: an EOF is an EOF. The bucket shouldn't mask over
that based on how it happened to be read.
If the filter / brigade / whatever, wants to interpret EOF in different ways
(e.g. make it an EOS), then that is fine. But the bucket shouldn't be used
as a compensating mechanism for that.
Cheers,
-g
--
Greg Stein, http://www.lyra.org/
