Nope. I'll have to look at it in more detail to know why anything would be happening with this attribute---especially since in most rules, the exact same 'p' instance is used for everything. Hmmm. Curious.
Cheers, Dave On Tue 23/09/08 5:40 PM , "Bart Whiteley" [EMAIL PROTECTED] sent: > > > I'm using ply-2.5. > > > > I have defined a p_error(p) function. For some parse errors, p (a > > LexToken) has a 'lexer' attribute. For other parse errors, p (still a > > LexToken) does not have a 'lexer' attribute. If I set a break point > > with pdb within p_error(), the stack traces look the same for both > > types of parse errors. > > > > Any idea why the LexToken argument to p_error() would lack the 'lexer' > > attribute at times? > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
