> Plan B would be to go the other way --- sed 's/parse error/syntax error/'
> --- so as to get consistent results from all post-1.50 Bisons. However
> I am concerned that this will needlessly break client-side code.
> (If you grep for 'parse error' in our sources you will find it a lot
> more places than just the regression tests Neil originally fingered;
> and that's not even counting the code that now lives on gborg.)
We've given people enough backwards-compatibility pain for one lifetime -
keep it as parse error...
Chris
