Thank you for alle the surgestions!
print@_{sort keys %_},$/if%_=split//,'= & *a?b:e\f/h^h!j+n,o@o;r$s-t%t#u'
This REALLY says all about my relations to parsers! :-(
I've gone for the YAPP and taken the Calp.yp example and replaced the grammer with the CCL grammer (leaving out the "Set" statement for now). Compiled it using:
yapp -v myParser.yp
with one message:
1 shift/reduce conflict
Then I've written a test:
use MyParser;
$parser=new MyParser();
$value=$parser->YYParse(yylex => \&lexer_sub, yyerror => \&error_sub
+);
$nberr=$parser->YYNberr();
$parser->YYData->{DATA}= [ 'a and ( b or c)' ];
$data=$parser->YYData->{DATA}[0];
All this gives is a:
Syntax error.
Can't locate object method "new" via package "MyParser" (perhaps you f
+orgot to l
oad "MyParser"?) at myparser.pl line 2, <STDIN> line 1.
- How do I really activate this parser?
- How do I add my functions to process the searching?
"If there are two or more ways to do something and one of them can lead to a disaster, then one or more persons will do it"
Edgar A. Murphy, Captain in U.S. Air Force (1949)
-
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.
|