Author: larry
Date: Sun Oct 8 22:34:45 2006
New Revision: 12874
Modified:
doc/trunk/design/syn/S04.pod
Log:
Ordinary undef is not an undefined generator, only unthrown exceptions are.
Modified: doc/trunk/design/syn/S04.pod
I'm experimenting with better forms of OO in PIR. I want to add a
get_parents() method on the Class PMC. Normally, I'd do something like the
attached patch, but the attached example file I use for testing shows that it
doesn't work for me.
I dug around a bit and couldn't find a reason for why
Jonathan~
On 10/7/06, Jonathan Lang <[EMAIL PROTECTED]> wrote:
TSa wrote:
> Dispatch depends on a partial ordering of roles.
Could someone please give me an example to illustrate what is meant by
"partial ordering" here?
Sets demonstrate partial ordering. Let < denote the subset relation shi
Author: larry
Date: Sun Oct 8 16:51:56 2006
New Revision: 12873
Modified:
doc/trunk/design/syn/S02.pod
Log:
Allow Perl-consistent :foo and # policies within «...»
Modified: doc/trunk/design/syn/S02.pod
==
--- doc/tr
From: Bob Rogers <[EMAIL PROTECTED]>
Date: Sat, 7 Oct 2006 18:52:29 -0400
. . .
Also, the "[oops; got 4 and X]" lines in the output seem to suggest
that Parrot may be getting confused about parameters. The "4" is really
the length of one of the coro structures, which must be
In a message dated Wed, 4 Oct 2006, Smylers writes:
Trey Harris writes:
I remember not so many years ago when there were a lot of modules
floating around that required you to do "no strict" of various flavors
in order to use them.
Really? How?
I wrote imprecisely. Not to "use" them in the
demerphq skribis 2006-10-08 16:01 (+0200):
> If its not obvious why this would be nice: qw() is often used as a
> list constructor for things like options or hash elements, and it
> would be convenient to have a way to selectively comment out certain
> elements. In perl 5 you have to C&P out the of
Smylers wrote:
Jonathan Lang writes:
> If you expected it to be a string, why did you use curly braces?
Because it isn't possible to learn of all Perl (5 or 6) in one go. And
in general you learn rules before exceptions to rules.
Agreed.
In general in Perl the replacement part of a substitu
A long while back Damian said I should follow up on the subject of
comments in qw// like constructs, and how useful they would be.
So im following up. Juerd said this is the right place.
If its not obvious why this would be nice: qw() is often used as a
list constructor for things like options o
Damian Conway wrote:
> Delimited blocks are bounded by C<=begin> and C<=end> markers...
> ...Typenames that are entirely lowercase (for example: C<=begin
> head1>) or entirely uppercase (for example: C<=begin SYNOPSIS>)
> are reserved.
I'm not a great fan of this concept of "reservation" when the
# New Ticket Created by Will Coleda
# Please include the string: [perl #40472]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=40472 >
The large portion of the languages/APL test suite is currently failing.
Failed Test
The only thing that I'd like to see changed would be to allow a more
flexible syntax for formatting codes - in particular, I'd rather use
something analogous to the 'embedded comments' described in S02,
replacing the leading # with an appropriate capital letter (as defined
by Unicode) and insistin
This week on the Perl 6 mailing lists
"When I first read 'Warnock applies' on things in p6 summaries a year
or so ago, I thought it was some really energetic programmer who went
around and applied patches as soon as people posed a question."
-- Carl M??sak, on Warnock's Dilemma
From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Sun, 8 Oct 2006 13:14:22 +0200
Am Sonntag, 8. Oktober 2006 03:52 schrieb Bob Rogers:
> Sounds good to me. But in that case, outer_ctx is not much better
> . . . but that's probably a much bigger job.
>
> In any case, I discov
S03 says that hypers recurse into subarrays.
That's a nice and useful feature, but that not-recursing is even more
useful. Especially given that many objects will probably does Array, you
want to be explicit about recursion.
S03 doesn't give a way to avoid recursion.
I suggested on #perl6 that
Am Sonntag, 8. Oktober 2006 04:25 schrieb chromatic:
> I'm doing more work on the embedding interface. Given that some Parrot
> functions may legitimately send and receive PMCs, what are the implications
> for garbage collection?
If a PMC isn't stored into some other structure, it has to be regis
Am Sonntag, 8. Oktober 2006 03:52 schrieb Bob Rogers:
> Sounds good to me. But in that case, outer_ctx is not much better
> . . . but that's probably a much bigger job.
>
> In any case, I discovered that Lua fails ~300 test cases with this
> patch. So, if we still consider it worth dropping th
I liked it. Just one nit, near the end:
>You can also preconfigure L, by
>naming them with a pair of angles as a suffix. For example:
>
> =comment Always allow E<> codes in any (implicit or explicit) V<>
> code... =config V<> :allow
>
> =comment All code to be italiciized...
Smylers schreef:
> in
> this particular case the particular behaviour involves _executing as
> Perl code something which the programmer never intended to be code in
> the first place_. That's crazily dangerous.
I wouldn't mind eval() to be off by default, so to have to put a "use
eval" in every
Jonathan Lang writes:
> Smylers wrote:
>
> > Jonathan Lang writes:
> >
> > > Translating this to perl 6, I'm hoping that perl6 is smart enough
> > > to let me say:
> > >
> > >s(pattern) { doit() }
> > >
> > > Instead of
> > >
> > >s(pattern) { { doit() } }
> >
> > That special case is n
Smylers wrote:
Jonathan Lang writes:
> Translating this to perl 6, I'm hoping that perl6 is smart enough to
> let me say:
>
>s(pattern) { doit() }
>
> Instead of
>
>s(pattern) { { doit() } }
That special case is nasty if you don't know about it -- you
inadvertently execute as code somet
Here's a patch that gets the Minesweeper examine running again. It's not
*correct*, in that the field-drawing math appears to do the wrong thing, but
I couldn't find the easy way to fix that. Maths is hard.
I cleaned up just enough of the code to get it to do the wrong thing without
crashing.
Jonathan Lang writes:
> Translating this to perl 6, I'm hoping that perl6 is smart enough to
> let me say:
>
>s(pattern) { doit() }
>
> Instead of
>
>s(pattern) { { doit() } }
That special case is nasty if you don't know about it -- you
inadvertently execute as code something which you
23 matches
Mail list logo
