Hello,
Sometimes I supply parameter debug=2 to the parse(...) method. I use to get
something like this:
. LexToken(MODEL,'model',1,0) shift state 3
MODEL . LexToken(IDENTIFIER,'TankControllerCIF',1,6) shift state 8
MODEL IDENTIFIER . LexToken(EQ,'=',1,24) shift state 14
MODEL IDENTIFIER EQ . LexToken(LCSCOPE,'|[',2,26) shift state 21
MODEL IDENTIFIER EQ LCSCOPE . LexToken(EXTERN,'extern',2,29) shift state 30
MODEL IDENTIFIER EQ LCSCOPE EXTERN . LexToken(VAR,'var',2,36) shift state 72
MODEL IDENTIFIER EQ LCSCOPE EXTERN VAR . LexToken(IDENTIFIER,'V',2,40)
shift state 18
MODEL IDENTIFIER EQ LCSCOPE EXTERN VAR IDENTIFIER .
LexToken(COLON,':',2,41) reduce 12
This has now become:
State : 0
Stack : . LexToken(MODEL,'model',1,0)
Action : Shift and goto state 3
State : 3
Stack : MODEL . LexToken(IDENTIFIER,'TankControllerCIF',1,6)
Action : Shift and goto state 8
State : 8
Stack : MODEL IDENTIFIER . LexToken(EQ,'=',1,24)
Action : Shift and goto state 14
State : 14
Stack : MODEL IDENTIFIER EQ . LexToken(LCSCOPE,'|[',2,26)
Action : Shift and goto state 21
State : 21
Stack : MODEL IDENTIFIER EQ LCSCOPE . LexToken(EXTERN,'extern',2,29)
Action : Shift and goto state 30
State : 30
Stack : MODEL IDENTIFIER EQ LCSCOPE EXTERN . LexToken(VAR,'var',2,36)
Action : Shift and goto state 72
State : 72
Stack : MODEL IDENTIFIER EQ LCSCOPE EXTERN VAR .
LexToken(IDENTIFIER,'V',2,40)
Action : Shift and goto state 18
State : 18
Stack : MODEL IDENTIFIER EQ LCSCOPE EXTERN VAR IDENTIFIER .
LexToken(COLON,':',2,41)
Action : Reduce rule [identifiers -> IDENTIFIER] with ['V'] and goto state
12
Result : [<Identifier:
.idName = 'V'
>]
This is not really a problem, except for the 'Result : ...' part, which
can become large (as in several 'pages' of console output) for large objects
returned from
parsing rules. Is there any way to hide just the 'Result : ...' lines?
Dennis
David Beazley wrote:
>I've put up a first release candidate of PLY-3.0 at:
>
> http://www.dabeaz.com/ply/ply-3.0rc1.tar.gz
>
>This version of PLY provides compatibility with Python 2.2-3.0.
>Except for the removal of a few undocumented features, it
>should be backwards compatible with prior versions of PLY.
>
>Why a new version number? A huge part of the internal
>implementation has been reorganized to simplify
>further maintenance, testing, and debugging. These changes
>were so significant a new version number seemed in order.
>
>I would appreciate feedback from current PLY users. Please
>check it out and let me know if it works with your existing code
>(or not).
>
>Cheers,
>Dave
>
>
>
>
>>
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"ply-hack" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/ply-hack?hl=en
-~----------~----~----~----~------~----~------~--~---
