On Sun, 27 May 2001, barries wrote:
> > there are Apache::Filter::{TIEHANDLE,PRINT} methods, the tie just isn't
> > done automatic for you.
>
> I guess the question is really: why not tie them automatically, given
> that there's not much use for STDIN and STDOUT in the context of a
> filter, it doesn't preclude other I/O methods, and it reduces the
> complexity of writing a filter?
no reason not to, just hasn't been done yet.
> > partly because the tied interface isn't complete.
>
> As of 5.6.x (ie now that BINMODE, EOF, SEEK, and TELL are there), what
> incompletenesses are there, and which would bite? I guess the question
> is, how far back in the perl 5.x family are you aiming to support more
> or less "fully"?
i meant the Apache::Filter tied interface isn't complete. there is only
PRINT for output filters, and nothing for input filters.
another reason auto-tie and the rest of the tie interface hasn't been done
is that i want to be careful to avoid bloat. the tie stuff should be
optional, at least at first, enabled with something like
PerlOptions +TieFilters
that does the tie and pulls in Apache::FilterTie or somesuch where all the
tie handle methods exist. we could make tied filters the default, but
things should be separated enough so PerlOptions -TieFilters can be done
cleanly.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
