Wow, very impressive. ++!
// <-[\n]>*:
I'd really want to take advantage of the new \N:
// \N*
foreach my $function (@functions) In Perl6, foreach will just be for. The C-style for loop will be called loop. And the for syntax will slightly change:
for @functions -> my $function {
...
}
rule quoted_string ($type)
{
$type
[
<-[$type]>*:
|
[ <after \\ > $type ]
]*
$type
}
Why not already have both types there?
rule quoted_string {
$delimiter := ( <['"]> )
[
<!before $delimiter> .
|
<after \\> $delimiter
]*
$delimiter
}
Hmm - In current regex stuff, I'd probably have written: /(['"]) (?: (?! \\ | \1) . | \\ . )* \1/x. Why not use something like that? (Or is it just a matter of taste?)
rule quoted_string {
$delimiter := ( <['"]> )
[
<!before \\ | $delimiter> .
|
\\ .
]
$delimiter
}
- Yes, I reinvent wheels.
- Spam: Visit eurotraQ.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|