This may not be all that robust, but it is better than square one...
#!/usr/bin/perl -w
use strict;
use Parse::RecDescent;
my $grammar = join( '', <DATA> );
my $parser = Parse::RecDescent->new( $grammar ) or
die "Error: Bad grammar\n";
my $text =<< "SUB_STDIN";
A nicely [[spaced]] link.
A poorly[[spaced]]link.
Another poorly..[[spaced]]..link.
A harder problem [spaced] link.
Yet harder still..]]spaced[[..link.
The real problem is [[spaced]] followed by ]] or [[ link.
SUB_STDIN
my $results = $parser->startrule( $text ) or
die "Error: Bad text\n";
__DATA__
startrule:
<skip:''> bit(s)
bit:
eol
| word
| space
| token
| punct
eol:
/\n[ \t]*/
{print "<newline>\n" }
space:
/[ \t]+/
{print "< >" }
word:
/[\w\']+/
{print "<word: $item[1]>" }
punct:
/[^\w\s\[\]]+/
{print "<punct: $item[1]>" }
| /(?<!\[)\[(?!\[)/
{print "<punct: $item[1]>" }
| /(?<!\])\](?!\])/
{print "<punct: $item[1]>" }
| /(?<!\[\[)\]\]/
{print "<punct: $item[1]>" }
| /(?<!\]\])\[\[/
{print "<punct: $item[1]>" }
token: link
link:
/\[\[(.+?)\]\]/
{print "<link: $item[1]>" }
Notice: new test cases for bracket as 'punct'.
--hsm
"Never try to teach a pig to sing...it wastes your time and it annoys the pig."
-
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.
|