On Thu, 13 May 2004, Dan Sugalski wrote:
>
> The big problem is that I don't know *how* to implement a mixed-type
> parser generator. I'm not big on parsers in general, so I'm mostly
> stuck with the literature if I need to write one from scratch.
I have been thinking the following about what lar
On Wed, 12 May 2004, Larry Wall wrote:
> In fact, I'd go so far as to say that it's almost impossible to do
> recursive descent when you allow for defining new operator precedence
> levels on the fly as Perl 6 does.
>
> : Operator precedence can be done in
> : a recdescent grammar straightforward
On Mon, 10 May 2004, Steve Fink wrote:
> use File::Basename qw(dirname);
> use lib dirname($INC{"P6C/Parser.pm"})."/../../../../lib";
I had already tried that, and it doesn't seem to work. I guess it is some
timing issue: $INC{"P6C/Parser.pm"} gets defined after P6C::Parser.pm is
loaded (I
On Sat, 8 May 2004, Abhijit A. Mahabal wrote:
> I was writing a few tests for the P6 parser and ran into a weird problem.
> If I have the following in a file in languages/perl6, it works as
> expected:
[...]
> Now, if I put exactly the same contents in a file in
> languages/perl6
I was writing a few tests for the P6 parser and ran into a weird problem.
If I have the following in a file in languages/perl6, it works as
expected:
The file contains:
===
use P6C::Parser;
use Perl6grammar;
my $grammar = new Perl6grammar;
print $grammar->sigil('$'),"\n";
print $grammar->
A12 has just come out P6C may be
heavily under construction, and I don't want to be in the way...
--Abhijit
Abhijit A. Mahabal http://www.cs.indiana.edu/~amahabal/Index: languages/perl6/P6C/Builtins.pm
===
RCS file: /cvs/p
====
--Abhijit
Abhijit A. Mahabal http://www.cs.indiana.edu/~amahabal/
A very basic newbeish question..
> >
> >>[EMAIL PROTECTED]:~/parrot$ tools/dev/parrotbench.pl -regex oo -conf
> >>../parrotbench.conf
> >>parrot perlpython ruby
> >>oo1 100%39% 23% -
> >>oo2 100%40% 22% -
> >>
Are bigger numbers more desirable (as the
