Dan says:
>'Kay, here's the thought. Exactly one filter may be (optionally) marked as
>an interpreter terminal filter. It runs in the context of the interpreter
>that made the I/O request, and gets (or returns) a real PMC. All the other
>filters run in the context of a separate interpreter, and wh
At 03:36 PM 12/18/2001 -0500, Melvin Smith wrote:
>Dan writes:
> >*) Filehandles get treated like arrays. Filters (which will be plain
> >coderefs) can be push/pop/shift/unshift/spliced onto them.
>
>By coderef I'm assuming you mean something like this Perl pseudo code...
>
>sub filter_dos_newlin
Dan writes:
>*) Filehandles get treated like arrays. Filters (which will be plain
>coderefs) can be push/pop/shift/unshift/spliced onto them.
By coderef I'm assuming you mean something like this Perl pseudo code...
sub filter_dos_newlines {
my $pmc = shift;
my $op = shift;
if( $
At 12:04 AM 12/15/2001 -0500, [EMAIL PROTECTED] wrote:
>Can we start some dialogue about stream filters?
>What form they take, are we talking regular expressions, etc.
Yes, we can. Here's what I'm thinking of.
*) Filehandles get treated like arrays. Filters (which will be plain
coderefs) can be
On Sat, Dec 15, 2001 at 12:04:17AM -0500, [EMAIL PROTECTED] wrote:
> Can we start some dialogue about stream filters?
Uh, I dunno, are we really at a point where it makes sense to do so?
--
Premature optimization is the root of all evil.
-- D.E. Knuth
Can we start some dialogue about stream filters?
What form they take, are we talking regular expressions, etc.
-Melvin
