On 2009 Feb 6, at 6:24, Daniel Ruoso wrote:
Em Sex, 2009-02-06 às 02:07 -0500, Brandon S. Allbery KF8NH escreveu:
I would think fcntl() is just the Unix version of a more general
concept, which is probably wider than POSIX.
Maybe this wider concepts can be expressed in their own roles, as
alr
Em Sex, 2009-02-06 às 02:07 -0500, Brandon S. Allbery KF8NH escreveu:
> >> +=head2 IO::POSIX
> >> +
> >> +Indicates that this object can perform standard posix IO operations.
> > I don't like that wording, but getting it right seems tricky.
> Do we want/need to deal with POSIX conformance levels?
On 2009 Feb 4, at 12:56, Leon Timmermans wrote:
On Wed, Feb 4, 2009 at 4:37 PM,
wrote:
+=item method IO dup()
Do we really want that? POSIX' dup does something different from what
many will expect. In particular, the new file descriptors share the
offset, which can result in some really con
On 2009 Feb 4, at 11:45, Aaron Crane wrote:
FWIW, I prefer the traditional spelling, "writable". Google suggests
that "writeable" is more common on the web, though; 4.8 versus 3.7
Mghits.
I have to admit that "writable" suggests to me that you can serve a
writ on it; an unlikely case for eve
Leon Timmermans writes:
> On Wed, Feb 4, 2009 at 4:37 PM, wrote:
> > +=item method IO dup()
>
> Do we really want that?
If we label a thing as "POSIX", it should certainly make all the POSIX
functionality available, IMHO. I'd consider arguments that we should
pick different names for specific
On Wed, Feb 4, 2009 at 4:37 PM, wrote:
> +=head2 IO
> +
> +The base role only tags that this is an IO object for more generic
> +purposes. It doesn't specify any methods or attributes.
> +
Shouldn't IO::readable and IO::Writable do IO?
> +
> +=head2 IO::Closeable
> +
I still think this should
Daniel Ruoso writes:
> Em Qua, 2009-02-04 às 16:45 +, Aaron Crane escreveu:
> > pugs-comm...@feather.perl6.nl writes:
> > > +=item method Int read($buf is rw, int $length)
> > I'm not sure that using a native int is the right thing here. If
> > whatever the implementation uses as int is narrow
Em Qua, 2009-02-04 às 16:45 +, Aaron Crane escreveu:
> pugs-comm...@feather.perl6.nl writes:
> > +=item method Int read($buf is rw, int $length)
> I'm not sure that using a native int is the right thing here. If
> whatever the implementation uses as int is narrower than size_t, that
> forces t
pugs-comm...@feather.perl6.nl writes:
> +=item method Int read($buf is rw, int $length)
I'm not sure that using a native int is the right thing here. If
whatever the implementation uses as int is narrower than size_t, that
forces the programmer to use an Int and do the necessary loop.
On the oth
Author: ruoso
Date: 2009-02-04 16:37:16 +0100 (Wed, 04 Feb 2009)
New Revision: 25182
Modified:
docs/Perl6/Spec/S16-io.pod
Log:
[spec/S16] proposed role-based api
Modified: docs/Perl6/Spec/S16-io.pod
===
--- docs/Perl6/Spec/S16-io.
10 matches
Mail list logo
