On Mon, Dec 01, 2008 at 03:33:47PM -0800, Chip Salzenberg wrote: > On Tue, Dec 02, 2008 at 12:22:38AM +0100, Johan Vromans wrote: > > [Quoting Chip Salzenberg, on December 1 2008, 15:16, in "Re: [perl #1154] -pi"] > > > The other of them would be less hacky but perhaps not efficient enough for > > > some purposes. Perl code can open ARGV and ARGVOUT and/or assign tied > > > filehandles to them. Then all the <> processing, period, happens via > > > "normal" (ahem) tied filehandle magic. This is something that could be done > > > today, modulo the '<> in list context' problem mentioned in overload.pm. > > > > And modulo the eof() facility. > > Couldn't the distinction between C<eof> on the one hand, and C<eof()> (which > is the same as C<eof(ARGV)>) on the other hand, be handled entirely in > pp_eof? The current tied EOF feature would then be adequate, no? Hrm. I think I'm all wet here. -- Chip Salzenberg twitter:chipsalz "UTOPIA PLANITIA IS IN ORBIT is the new HAN SHOT FIRST" - Crisper Than ThouThread Previous | Thread Next