On Tue, Jan 09, 2007 at 09:33:52AM -0800, Larry Wall wrote:
> The Perl 6 perspective on this is that error values should be allowed to
> be as "interesting" as you like. The lower level routine goes ahead and
> pregenerates the exception object but returns it as an interesting
> error value inste
On Tue, Jan 09, 2007 at 10:28:22PM -0800, Allison Randal wrote:
: If both sync and async ops returned status objects, it would be
: conveniently consistent. It would also be annoyingly heavyweight for a
: simple synchronous operation, but then the biggest cost for I/O ops is
: generally the I/O.
Larry Wall wrote:
The Perl 6 perspective on this is that error values should be allowed to
be as "interesting" as you like. The lower level routine goes ahead and
pregenerates the exception object but returns it as an interesting
error value instead of throwing it. Then the calling code can ju
On Fri, Jan 05, 2007 at 10:59:59PM -0800, Allison Randal wrote:
: Jonathan Worthington wrote:
: >I suspect it's cheaper/easier for a compiler to generate code to check a
: >return value and throw an exception of its own choosing, than it is to
: >emit code to catch the exception and return the er
Jonathan Worthington wrote:
I like the look of this, but if I wanted to go about implementing it I
feel I'm kinda short of what that means implementation wise. I'm happy
enough with flattening composition and all that jazz, but a little extra
guidance on what you're expecting to compose into th
Allison,
Allison Randal wrote:
I've just moved pdd22 out of the clip directory, marking it as ready
for beginning implementation efforts.
Excellent! I've just read through it and like what I'm seeing.
Comments on the pdd are welcomed. A few things worth highlighting:
- I/O layers will be re
