and it is really only a question
of style.
I'd hate to see P:RD fall into same trap as regexps: P:RD doesn't need
to be a complete programming language. P:RD is fine as a perl
accessory.
yes it's really fine, even it it stays as it already is.
Regards
Charly
--
Karl Gaissmaier
Hi Yves, (and perhaps Damian, if he has time to read
until the end, sorry)
Orton, Yves schrieb:
oh fine, the next time I will look first in the source!
No. Read the docs first. Its there... :-)
Oh god, I red it, at least two times and also the FAQ. The next
time I use grep, sigh.
and
of ENTITY, if
e.g. the DECL subrule fails after already commited.
Is there a general usage pattern to shortcut the ENTITY rule
if an already commited subrule fails?
Best Regards
Charly
--
Karl Gaissmaier KIZ/Infrastructure, University of Ulm, Germany
Email:[EMAIL PROTECTED
code.
Best Regards
Charly
Andras
-Original Message-
From: Karl Gaissmaier [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 31, 2004 4:24 AM
To: PerlDiscuss - Perl Newsgroups and mailing lists
Subject: Re: Negative Look-ahead problem
PerlDiscuss - Perl Newsgroups and mailing lists
unreadable and hard to mainatin (the example is just
a shrink down extract in a huge grammar).
Hmm, any solutions with this - now more detailed - problem
in mind?
Best Regards
Charly
--
Karl Gaissmaier KIZ/Infrastructure, University of Ulm, Germany
Email:[EMAIL PROTECTED
Best Regards
Charly
--
Karl Gaissmaier KIZ/Infrastructure, University of Ulm, Germany
Email:[EMAIL PROTECTED] Service Group Network
Tel.: ++49 731 50-22499
Hi Andras
Karl Gaissmaier wrote:
hmmm, I've overseen that the global skip pattern
is qr/s*/, therefore ANDY is matched as a reserved
word too, since the token prefix can be just nothing.
To change the token prefix in the RESERVED rule
to s+ (-- see the + instead of *) should help:
Thank you
) is
reported at any time.
Best Regards
Charly
--
Karl Gaissmaier KIZ/Infrastructure, University of Ulm, Germany
Email:[EMAIL PROTECTED] Service Group Network
Karl Gaissmaier schrieb:
Hi,
I nearly finished Config::Scoped, yet another config
file parser but I am currently busy with an annoying
locale problem. I'm for example not able to match
german umlaute with the rule pattern /\w/ even with
the proper LC_... env and 'use locale' in P::RD.
With a plain
. The This is an error
message\n gets read into the variable as expected, but P::RD's error
messages are printed to STDERR nonetheless.
you can cheat P::RD with directly accessing $thisparser-{errors},
see the FAQ: 'Accessing error data' and the answer by Damian
Best Redards
Charly
--
Karl
10 matches
Mail list logo