[9fans] all you yacc experts

[bruce.ellis@gmail.com (Bruce Ellis)]

my motivation is that the limbo version of yacc is out of date
severely (doesn't cope with cc.y) and it seems like a good time to
have a 5c in limbo that copes with all and sundry arm variants - two
more were released this week - with loadable arch modules. and to
write shorter sentences.

brucee

On 13 November 2011 15:48, Lucio De Re <lucio at proxima.alt.za> wrote:
>> If all the information is available in y.output then surely modifying
>> yacc will cut out the middle man.
>>
> That's not quite how I remember it, I'm sure that there was no trivial
> way to alter the output from yacc to conform to the needs of Russ'
> error messages. ?That said, even if y.output does include the
> essentials, it would have been extremly insightful of Russ to design a
> message format that would be worth including in yacc itself. ?It
> certainly isn't the impression I got from looking at the available
> documentation and sources,
>
> I don't want to rain on anybody's parade, but I think a middle man
> provides more flexibility and allows the developers on the yacc side
> to focus on generating the type of output that makes the most sense,
> rather than what the Go toolchain requires.
>
>> On my list.
>
> Ron isn't the only developer that will benefit from your efforts, I'd
> like to show my appreciation as well.
>
> ++L
>
>
>



-- 
Don't meddle in the mouth -- MVS (0416935147, +1-513-3BRUCEE)