We're going to try something a little different. With Chip's blessing
I've written a very early draft of the PDD for I/O (not numbered
yet). The attached PDD isn't a completed document with Chip's seal of
approval, it's a seed for discussion.
What I need from you all is comments. What's mis
On Friday 03 March 2006 02:41, Tim Bunce wrote:
> Any news on this? Is it okay? Should I send it via parrotbug?
It looked good to me. I say check it in and see what the smokes do.
-- c
On Wednesday 01 March 2006 11:19, Beau E. Cox wrote:
> c - Did you have a chance to try my patch? If so,
> did it work?
It bypassed the build error, so that much definitely works better. I haven't
finished running the test suite to see if everything else works.
-- c
How do you verify that a print succeeded? Currently there's no way to
know. Throwing an exception if a global flag is set would suffice and
wouldn't require constantly pushing exception handlers in case the
program doesn't care enough (e.g. the run it and delete it variety).
Plus using excep
With respect to async IO (regretfully I get to see a lot of this at
$job):
Each operation can be async, or sync, with a similar API. There
should be enough hooks to be able to wait on a specific operation
happenning on a stream, any operation on a stream, any operation on
a group of streams, and a
Any news on this? Is it okay? Should I send it via parrotbug?
Tim.
On Tue, Feb 28, 2006 at 03:36:20PM +, Tim Bunce wrote:
> On Tue, Feb 14, 2006 at 10:04:59PM +0100, Leopold Toetsch wrote:
> > On Feb 14, 2006, at 18:29, Tim Bunce wrote:
> >
> > >The runtime dlfunc code will need to be altere
The tailcall op forces the old context to be recycled, which causes
mighty peculiar things to happen if the sub had created any closures,
since those closures still refer to the just-freed context. Sometimes
(but not always) the context is reused for the next call; when this
happens, it seems t
I think Perl 6 could use a wiki for several things:
1. creating a place where people can easily find user annotations
of the synopses etc
2. scratch pad areas for people to write musings, criticism,
discussion and so forth in a way that the community can revise. This
complements theh discussion p
