From: roar.foshaug@systor.st   
      
   > [There isn't any "official" way, just ways that are more or less bad.   
   > -John]   
      
   Apart from adding productions for common errors, to recognize and   
   handle them spesifically, the approach of identifying a   
   point-of-no-return state inside a grammar production seems to work for   
   the tests I've done so far.   
      
   The idea is that deciding that a production has reached a   
   point-of-no-return, changes the meaning of failure to match required   
   elements from that of simply aborting the attempt and letting the   
   calling production decide what to do, to instead reporting an error,   
   based on what required element (production or token) failed.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)