[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Proposal for lambda'ing error recovery

From: Akim Demaille
Subject: Re: Proposal for lambda'ing error recovery
Date: Tue, 19 Nov 2002 11:31:03 +0100
User-agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.2 (i386-pc-linux-gnu)

 >> From: Akim Demaille <address@hidden>
 >> Date: Tue, 19 Nov 2002 09:26:04 +0100
 >> Same here.  But really, I'd like to know what kind of parser (in
 >> particular what kind of actions is can perform) so that the mere
 >> spilling of some variables could have a noticeable impact :(
 >> I'm fine with the temporaries to avoid this issue though.

 Paul> A parser that has to run on a small, slow, low-power machine.
 Paul> (I happen to be developing for such a machine right now.)

Sorry, but I still don't understand :(  I completely misunderstand for
instance the relationship with the machine type: my claim is that the
manipulation of these variables is <<<< before the rest of the process
(user actions etc.).  Well, no, I don't claim it, I suspect it, but
have no evidence :(

 >> I see no means for the user to have some influence on this area of
 >> the code.  I did not try to refactor the *report* SyntaxError, just
 >> the *recover* bits.

 Paul> Hmm, but yy_recover_parse_error invokes YYFPRINTF, and the user can
 Paul> redefine YYFPRINTF.

What could be stolen?  In addition, YYFPRINTF is quite new, I doubt
people have found means to abuse of it.  And I honestly don't plan to
maintain abuses of internal guts.  yyerror is a very special case
where clearly Bison lacked proper support.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]