At 11:33 PM -0700 7/11/02, Sean O'Rourke wrote:
>It's time for my weekly post to this old thread. The grammar has
>grown enough to deserve more than one file, and is starting to change
>in new directions. For example, it's now Turing-complete, if you have
>a Parrot engine and a bit of spare time
On Fri, 2002-07-12 at 02:33, Sean O'Rourke wrote:
> What's currently "supported":
> - if/elsif/else (even "unless" and the feared "elsunless";)
When we talked about this last, I had been concerned about loops and
conditionals, but others had scoping concerns. Ok, perhaps there's no
way we can r
It's time for my weekly post to this old thread. The grammar has
grown enough to deserve more than one file, and is starting to change
in new directions. For example, it's now Turing-complete, if you have
a Parrot engine and a bit of spare time. Call it a primitive "demo
version" of some of Per
On Sat, 6 Jul 2002, Trey Harris wrote:
: In a message dated Sat, 6 Jul 2002, Sean O'Rourke writes:
: > - Implicit currying variables ($^a etc) are in. I thought I had read
: > somewhere they were gone in favor of closure args, but people seem
: > to be using them, and they're not hard to put
In a message dated Sat, 6 Jul 2002, Sean O'Rourke writes:
> - Implicit currying variables ($^a etc) are in. I thought I had read
> somewhere they were gone in favor of closure args, but people seem
> to be using them, and they're not hard to put in.
My understanding is that they still exist
Based on perlop(1) and the note at the end of apocalypse 3, here's a start
on a Parse::RecDescent grammar for Perl 6 expressions. It does not handle
some variables; in particular, qq/${"foo"}/ won't fly. It should handle
precedence and hyping when adding new operators in the "right way". To
add
At 09:29 PM 6/18/2002 +0200, Jerome Vouillon wrote:
>On Mon, Jun 17, 2002 at 04:59:05PM -0400, Melvin Smith wrote:
>I have started writing a Perl 6 grammar:
> http://www.pps.jussieu.fr/~vouillon/parrot/parser.y
>It is far from complete, and certainly not very accurate, but it may
>be a good st
On Tue, 18 Jun 2002, Jerome Vouillon wrote:
> On Mon, Jun 17, 2002 at 04:59:05PM -0400, Melvin Smith wrote:
> > The hole I see is not having a Perl6 grammar to toss about.
> > You must sift through the apoc/exe pile to formulate it. Regardless of
> > which approach is taken, I'd like to see a BNF
On Mon, Jun 17, 2002 at 04:59:05PM -0400, Melvin Smith wrote:
> The hole I see is not having a Perl6 grammar to toss about.
> You must sift through the apoc/exe pile to formulate it. Regardless of
> which approach is taken, I'd like to see a BNF style grammar floating around
> before we talk tools
At 06:55 PM 6/18/2002 +0200, Bart Schuller wrote:
>On Mon, Jun 17, 2002 at 03:43:48PM -0400, Melvin Smith wrote:
> > Ok, then we should start some nitty-gritty talk. I'm familiar with
> > implementing parsers for LR(1) grammars. I hope Larry, and other
> > people that have been digesting the Apoca
On Mon, Jun 17, 2002 at 03:43:48PM -0400, Melvin Smith wrote:
> Ok, then we should start some nitty-gritty talk. I'm familiar with
> implementing parsers for LR(1) grammars. I hope Larry, and other
> people that have been digesting the Apocalypses (I can't say I have)
> can fill us in about the ch
11 matches
Mail list logo
