If spaces delimit tokens,
/abc* def/ means in perl5
/abc*def/
or /(?:abc)*def/ ?
Thanks
Alberto
--
Alberto Manuel B. Simoes
Departamento de Informática - Universidade do Minho
http://alfarrabio.di.uminho.pt/~albie - http://numexp.sf.net
On 15 Jun 2002, Alberto Manuel Brandão Simões wrote:
>
> If spaces delimit tokens,
>
> /abc* def/ means in perl5
>
> /abc*def/
> or /(?:abc)*def/ ?
>
> Thanks
>
> Alberto
The former.
Now that it seems that Parse::RecDescent and, ultimately,
Parse::FastDescent, will be subsumed into the Perl 6 regex/grammar system,
I've been thinking about how to implement P::RD directives such as
, and ; or features such as tracing.
I've really only thought about , but am not sure if those t
On Sat, Jun 15, 2002 at 03:19:34PM +0200, Marcel Gruenauer wrote:
> Now, could you just do
>
> rule leftop ($leftop, $op) {
> <$leftop> [$op <$leftop>]*
> }
>
> rule leftop ($leftop, $op, $rightop) {
> <$leftop> [$op <$rightop>]*
> }
At the very least you sho
On Sat, Jun 15, 2002 at 09:08:31AM -0500, Jonathan Scott Duff wrote:
> At the very least you should be able to do this:
>
> rule leftop($leftop,$op;$rightop) {
> $other := { (defined $rightop) ?? $rightop :: $leftop }
> <$leftop> [$op <$other>]*
> }
Or maybe
On Sat, Jun 15, 2002 at 04:50:20PM +0200, Marcel Gruenauer wrote:
> On Sat, Jun 15, 2002 at 09:08:31AM -0500, Jonathan Scott Duff wrote:
>
> > At the very least you should be able to do this:
> >
> > rule leftop($leftop,$op;$rightop) {
> > $other := { (defined $rightop) ?? $rightop :
> Now, could you just do
>
> rule leftop ($leftop, $op) {
> <$leftop> [$op <$leftop>]*
> }
>
> rule leftop ($leftop, $op, $rightop) {
> <$leftop> [$op <$rightop>]*
> }
I should hope that rules can take multiple arguments. Here's something
that made me wonde
At 2:00 PM -0500 6/15/02, Jonathan Scott Duff wrote:
>With all this new syntax, I can't wait until there's a perl6 I can try
>it out against rather than just perl6-language.
Well, then, time to pitch in! :)
Seriously, Parrot's at a state where a not inconsiderable chunk of
perl 6 (and perl 5) c
Dan Sugalski:
# At 2:00 PM -0500 6/15/02, Jonathan Scott Duff wrote:
# >With all this new syntax, I can't wait until there's a perl6
# I can try
# >it out against rather than just perl6-language.
#
# Well, then, time to pitch in! :)
#
# Seriously, Parrot's at a state where a not inconsiderable
'set P3[I5],"foo"' finally works. This probably should have been done a
long time ago, but we had some miscommunication problems. True to my
previous word, t/pmc/perlarray.t has a new test running Pn[In] &c
through its paces.
The test only checks the first index, so be prepared for some more fixe
I'm writing the Parrot_destroy function in embed.c and I noticed that
some things like the stacks and the memory allocation system don't have
destructors, is there a reason for this?, or should I write them?
marcos
At 7:20 PM -0700 6/15/02, Marco Antonio Valenzuela Escárcega wrote:
>I'm writing the Parrot_destroy function in embed.c and I noticed that
>some things like the stacks and the memory allocation system don't have
>destructors, is there a reason for this?, or should I write them?
That part never go
Once nice thing about Java is the class naming convention that lets
individual companies (or even individuals, I guess) do custom development
that they can safely integrate with the "standard" Java classes and the work
of other companies/individuals without fear of namespace clashes. For
example,
On Sat, Jun 15, 2002 at 10:35:48PM -0400, John Siracusa wrote:
> Once nice thing about Java is the class naming convention that lets
> individual companies (or even individuals, I guess) do custom development
> that they can safely integrate with the "standard" Java classes and the work
> of other
On Sun, 16 Jun 2002, Michael G Schwern wrote:
> On Sat, Jun 15, 2002 at 10:35:48PM -0400, John Siracusa wrote:
> > Once nice thing about Java is the class naming convention that lets
> > individual companies (or even individuals, I guess) do custom development
> > that they can safely integrate w
15 matches
Mail list logo