It's quite possible with two different lexemes at the same location, for
one to accepted and the other discarded. The names of the lexemes are
confusing the issue/ But (if the messages are accurate) at line 3,
column 17, two lexemes are encountered, one named "whiteSpaceCharacter",
the other named "character". "whiteSpaceCharacter" is discarded, and
"character" is accepted.
By the way, it's helpful to me if you always mention which version is
referred to, and whether the issue seems to be new as of that version
(to the extent you know). Particularly when I've just released a new
version, my mindset is to wonder if the behavior described is a
regression, new with the release of a few hours ago. (My guess is that
in this case it's not.)
-- jeffrey
On 01/17/2014 09:47 PM, Durand Jean-Damien wrote:
Jeffrey,
Before eventually file a report, I'd like to know if this is possible
in Marpa to have this kind of output, i.e. a character from input
stream that is first discarded then accepted:
Attempting to read lexeme L3c5-16: alpha; value="ReEntryPoint"
Lexer "L0" accepted lexeme L3c5-16: alpha; value="ReEntryPoint"
Lexer "L0" rejected lexeme L3c17: anyCharExceptQuote; value=" "
Lexer "L0" discarded lexeme L3c17: whiteSpaceCharacter
Attempting to read lexeme L3c17: character; value=" "
Lexer "L0" accepted lexeme L3c17: character; value=" "
Thanks / JD.
--
You received this message because you are subscribed to the Google
Groups "marpa parser" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "marpa
parser" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
