lib/Parse/Yapp.pm

61 Through all your files, comments are either Perl style, introduced by I<#>
62 up to the end of line, or C style, enclosed between  I</*> and I<*/>.
83 any special character as such. '"', '$' and '@' will be automatically
87 You cannot have a literal I<'error'> in your grammar as it would
90 you should have written it I<error> and will treat it as if it were the
116 at the very beginning of the parser module. They are not as useful as
128 as they are implemented exactly the same way in Parse::Yapp)
139 as tokens, generating a syntax error if used in the left hand side of
141 Note that in Parse::Yapp, you I<don't> need to declare tokens as in yacc: any
142 symbol not appearing as a left hand side of a rule is considered to be
144 Other yacc declarations or constructs such as C<%type> and C<%union> are
169 as this is usually a mistake, and you will certainly have a reduce/reduce
183 Note that in Parse::Yapp, a lhs I<cannot> appear more than once as
205 single character, it is much more difficult in Perl, as there
229 $_[1] to $_[n] are the parameters just as $1 to $n in yacc, while
257 Note that if C<$_[0]-E<gt>YYCurtok> is declared as a C<%nonassoc> token,
311 the grammar as if you wrote (although @x-1 is not a legal lhs value):
351 They C<must> be returned as a list of two variables, the first one
355 as the parsing driver never use it but to call semantic actions:
368 Note that your lexer should I<never> return C<'error'> as token
380 If you want one, write it knowing that it is passed as parameter
385 resume parsing as if no error occured. Of course, since the invalid
389 The method C<$_[0]-E<gt>YYLexer> may help you, as it returns a reference
390 to the lexer routine, and can be called as
480 You can disable this feature by compiling your grammar with yapp using
505 as specified in the Perl README file.