On Mon, 16 Feb 2009, Daniel Ruoso wrote:

Em Sáb, 2009-02-14 às 18:01 +0100, Leon Timmermans escreveu:
On Sat, Feb 14, 2009 at 6:38 AM,  <pugs-comm...@feather.perl6.nl> wrote:
+=head2 IO::Openable
+This role implies that the object can be connected to, or listened on.
I'm not sure if I really hate or love this. I'm not quite convinced if
the use of it anyway.

Maybe I'm thinking sideways again, but I haven't thought of "open" as
being a method of any IO object, because usually "open" is the thing
that gets you an IO Object.

        [See my other e-mail to Leon for my comments on this].

One important thing here, is that the roles are not intended to
represent attributes of the object. For instance, IO::Readable and
IO::Writeable are not going to be composed depending on the parameters
you send to "open", but if you're in a Linux system, it should probably
return an object that does IO::Linux26 (which does IO::POSIX[$SomeLevel]
does IO::BSD[$Somewhat], which should also compose IO::Readable and
IO::Writeable independent of the open mode).

So you can have a stream handle which does IO::Writeable, but will throw an error on any attempt to write? Anyway, you've answered my question in the other e-mail.


| Name: Tim Nelson                 | Because the Creator is,        |
| E-mail: wayl...@wayland.id.au    | I am                           |

Version 3.12
GCS d+++ s+: a- C++$ U+++$ P+++$ L+++ E- W+ N+ w--- V- PE(+) Y+>++ PGP->+++ R(+) !tv b++ DI++++ D G+ e++>++++ h! y-

Reply via email to