ParrotInterpreter.stdhandle method

Patrick R. Michaud pmichaud at pobox.com
Mon Sep 20 15:17:37 UTC 2010


On Fri, Sep 17, 2010 at 01:48:21PM -0400, Andrew Whitworth wrote:
> http://trac.parrot.org/parrot/ticket/264
> 
> The last comment from Allison in that ticket recommends we break up
> the stdhandle method, which is not clearly named, into several
> individual methods for each standard handle: input, output, and error.
> However, NotFound suggested that some other discussion that was not
> included in the ticket came to an opposite conclusion: that we should
> rip this method out entirely and instead rely on some of the dynops in
> the io.ops set. I haven't been able, in a short search, to find any

The #parrotsketch discussion at 
http://irclog.perlgeek.de/parrotsketch/2010-06-08#i_2415916
seems to indicate that the getstd* ops are to permanently remain in 
the core opcode set.  I suspect the ticket was never updated with
this decision.

I'll update TT #264 with this information as well.

Pm


More information about the parrot-dev mailing list