On Fri, Nov 12, 2010 at 06:59:59PM -0800, Ben Goldberg wrote:
(snip plea to paint the bikeshed fuchsia)
The design of the I/O system will be chosen by the first person to implement
it. If you want any say in the matter, you need to be that person. Bonus
points if you also port at least one app t
On Nov 12, 2:21 pm, stefa...@cox.net (Stefan O'Rear) wrote:
> On Thu, Nov 11, 2010 at 05:47:46PM -0800, Ben Goldberg wrote:
> > I would like to know, is perl6 going to have something like select
> > (with arguments created by fileno/vec), or something like IO::Select
> > (with which the user doesn'
On Fri, Nov 12, 2010 at 8:21 PM, Stefan O'Rear wrote:
> This goes without saying. One caveat - it should be possible to pass
> integer file descriptors.
Integer file descriptions should exist in the POSIX module, just like
Win32 handles should exist in the Win32 module, but they don't have a
pla
On Fri, Nov 12, 2010 at 11:21:10AM -0800, Stefan O'Rear wrote:
> TIMTOWDI. Perl without system calls is not Perl.
+1
> This is why S16 is junk - too much blue-sky thinking, not enough
> pragmatism and practical experience.
Agreed.
> Forbidding things out of idealistic concerns like API purity
On Thu, Nov 11, 2010 at 05:47:46PM -0800, Ben Goldberg wrote:
> I would like to know, is perl6 going to have something like select
> (with arguments created by fileno/vec), or something like IO::Select
> (with which the user doesn't need to know about the implementation,
> which happens to be done
Hi,
Am 12.11.2010 02:47, schrieb Ben Goldberg:
I would like to know, is perl6 going to have something like select
(with arguments created by fileno/vec), or something like IO::Select
(with which the user doesn't need to know about the implementation,
which happens to be done with fileno/vec/sele
