Re: Open and close brackets read as single token
- From: Thomas Revell <tom@xxxxxxxxxxxxx>
- Date: Mon, 23 Jan 2006 21:20:18 GMT
Thomas Revell wrote:
>> Otherwise, did you try turning the debug tracing on, and analyzing
>> the
>> output?
>
> Nope, but you're right, I should've done. I'll give that a try now.
And now have done. It looks as though the () string is being recognised as a
possible "string literal match". The section of the debug output that looks
relevant (to me, at least) is below (all debug options were on):
Consumed token: <<DEFFN>: "DEF FN">
Call: Function_Definition
Current character : ( (40)
Currently matched the first 1 characters as a "(" token.
Possible string literal matches : { "()" }
Current character : ) (41)
No more string literal token matches are possible.
Currently matched the first 2 characters as a "()" token.
****** FOUND A "()" MATCH (()) ******
Consumed token: <<NUMERIC_IDENTIFIER>: "q">
Current character : = (61)
No more string literal token matches are possible.
Currently matched the first 1 characters as a "=" token.
****** FOUND A "=" MATCH (=) ******
To me, it's looking more and more like I've somehow accidentally defined
"()" as a valid token in itself. I can't find where though (I've listed all
of the tokens in my reply to Ben Segall).
Tom.
.
- Follow-Ups:
- Re: Open and close brackets read as single token
- From: Ben Segall
- Re: Open and close brackets read as single token
- References:
- Open and close brackets read as single token
- From: Thomas Revell
- Re: Open and close brackets read as single token
- From: Oliver Wong
- Re: Open and close brackets read as single token
- From: Thomas Revell
- Open and close brackets read as single token
- Prev by Date: Re: Open and close brackets read as single token
- Next by Date: Re: Open and close brackets read as single token
- Previous by thread: Re: Open and close brackets read as single token
- Next by thread: Re: Open and close brackets read as single token
- Index(es):
Relevant Pages
|
|