te:
> On Wed, Dec 30, 2009 at 1:05 PM, Marcel Laverdet
> wrote:
>>
>>
>>> Do you actually mean '.' matches non newline?
>>
>> Yes, apologies :)
>>
>>> I made some corrections. Now yylval_string.l becomes the following.
You
>> said
nexpected token
UNEXPECTED_CHARACTER on line 5".
On Wed, 30 Dec 2009 09:39:30 -0600, Peng Yu wrote:
> On Wed, Dec 30, 2009 at 12:54 AM, Marcel Laverdet
> wrote:
>>
>>
>> 1) [:space:] is a character class expression. If you want one or more
>> spaces you would d
1) [:space:] is a character class expression. If you want one or more
spaces you would do [[:space:]]+. What your scanner is looking for right
now is one of either ":, s, p, a, c, or e". Does that make sense? Just wrap
it in another set of []'s
2) . only matches newline, the documentation is not
4, 2008, at 10:53 AM, Hans Aberg wrote:
On 14 Nov 2008, at 19:35, Marcel Laverdet wrote:
This is a pretty good idea, but I'm not sure if it's possible. For
instance in the case of an if statement I modified my grammar as
such:
if_statement:
t_IF t_LPAREN expression t_RPAREN {yy
ion rule so the lexer can't adjust in time.
On Nov 11, 2008, at 11:08 AM, Hans Aberg wrote:
On 11 Nov 2008, at 08:10, Marcel Laverdet wrote:
It's unclear here whether the child of the if statement should be
an empty Block or an empty ObjectLiteral. The ECMAScript spec
Hello. I'm writing a parser for ECMAScript (http://www.mozilla.org/js/language/E262-3.pdf
) in Bison right now and I'm having some problems dealing with
ambiguities in the language. The relevant portions of my grammar are
as follows:
statement_list:
source_element
| statement
