On 2009 Feb 16, at 22:44, Timothy S. Nelson wrote:
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.
Not sure what you're getting at, but the obvious example is a
writeable h
Daniel Ruoso wrote:
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.
I'd expect the plain "open" to be really a sub (maybe a "is export"
method in the generic IO role), that doe
I didn't realise this hadn't gone to the list. Enjoy, all :).
-- Forwarded message --
Date: Tue, 17 Feb 2009 14:34:07 +1100 (EST)
From: Timothy S. Nelson
To: Leon Timmermans
Subject: Re: r25328 - docs/Perl6/Spec
On Mon, 16 Feb 2009, Leon Timmermans wrote
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, 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 quit
Em Sáb, 2009-02-14 às 18:01 +0100, Leon Timmermans escreveu:
> On Sat, Feb 14, 2009 at 6:38 AM, 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 anyw
On Sun, 15 Feb 2009, Brandon S. Allbery KF8NH wrote:
On 2009 Feb 15, at 22:50, Timothy S. Nelson wrote:
On Sat, 14 Feb 2009, Leon Timmermans wrote:
+=item sysopen
I vote for sysopen (and all other sys functions) to be wiped out of
existence.
Disagree -- I think these belong in IO::Unbuffe
On 2009 Feb 15, at 22:50, Timothy S. Nelson wrote:
On Sat, 14 Feb 2009, Leon Timmermans wrote:
+=item sysopen
I vote for sysopen (and all other sys functions) to be wiped out of
existence.
Disagree -- I think these belong in IO::Unbuffered. Maybe we could
make that optional, though
I
On Sat, 14 Feb 2009, Leon Timmermans wrote:
On Sat, Feb 14, 2009 at 6:38 AM, wrote:
+=head2 IO::Openable
+
+This role implies that the object can be connected to, or listened on.
+
+=over 4
+
+=item open
+
+ method Bool open();
+
+Attempts to open the handle. Depending on the implementation,
On Sat, Feb 14, 2009 at 10:31 PM, Brandon S. Allbery KF8NH
wrote:
>
> I think the point here is that on POSIX systems that gets you ioctl() and
> fcntl(), and on non-POSIX systems either they don't exist or they throw
> runtime errors. Aside from my earlier suggestion that non-POSIX systems
> gen
On 2009 Feb 14, at 12:01, Leon Timmermans wrote an unending refrain of:
Why should this do POSIX? What about non-POSIX operating systems?
I think the point here is that on POSIX systems that gets you ioctl()
and fcntl(), and on non-POSIX systems either they don't exist or they
throw runtim
On Sat, Feb 14, 2009 at 6:38 AM, wrote:
> +=head2 IO::Openable
> +
> +This role implies that the object can be connected to, or listened on.
> +
> +=over 4
> +
> +=item open
> +
> + method Bool open();
> +
> +Attempts to open the handle. Depending on the implementation, this could be
> an open(
11 matches
Mail list logo
