>>>>> "J" == Juerd  <[EMAIL PROTECTED]> writes:

  J> Rob Kinyon skribis 2005-05-04 11:20 (-0400):
  >> $h.print() goes to $h.out
  >> $h.readline() goes to $h.in
  >> $h.warn() goes to $h.err
  >> Making the tri-directional trifecta complete.

  J> It's sort-of consistent, but I don't like it, because warnings are much
  J> more complicated than just things that are printed to stderr.

also you have the .err backwards. in the case of running a subprocess,
the err handle is readonly (the subprocess writes to ITS stderr with
warn). so you need another method to make a easy read of the err handle.

and you need ways to get at the handles themselves so you can use
sysread/write, select/poll and event loops. but i like the idea of
returning a single smart object which returns reasonable things in
appropriate contexts.

remember at all times when discussing i/o for p6 that the goals are to
support all forms of i/o in a consistant manner. it is much more than
just a polymorphic open or io::all. they only address one aspect of i/o
(initiating an i/o request) and that skips read/write/fcntl/event loops
and more.


Uri Guttman  ------  [EMAIL PROTECTED]  -------- http://www.stemsystems.com
--Perl Consulting, Stem Development, Systems Architecture, Design and Coding-
Search or Offer Perl Jobs  ----------------------------  http://jobs.perl.org

Reply via email to