>>> "Tim" == Tim Van Holder <[EMAIL PROTECTED]> writes:
> I don't see how _bison_ can do this with any accuracy
Well, with enough insight on locations, I don't see why it couldn't.
Of course it requires changes. One possibility is the one you
mention, which is quite tractable for small files, b
Akim Demaille wrote:
"Frans" == Frans Englich <[EMAIL PROTECTED]> writes:
> > Opening the source and printing it is surely a good idea and a very nice
> > complement to regular reporting, but I still think that improving regular
> > reporting is significant.
>
> I was not proposing to re
>>> "Frans" == Frans Englich <[EMAIL PROTECTED]> writes:
> On Friday 15 September 2006 08:43, Akim Demaille wrote:
>> >>> "Frans" == Frans Englich <[EMAIL PROTECTED]> writes:
>> >
>> > I guess one would have to invent a different "print system" for
>> > that. Perhaps those "error printers" wo
On Friday 15 September 2006 08:43, Akim Demaille wrote:
> >>> "Frans" == Frans Englich <[EMAIL PROTECTED]> writes:
> >
> > I guess one would have to invent a different "print system" for
> > that. Perhaps those "error printers" would return a heap allocated
> > char string, which the caller(the
>>> "Frans" == Frans Englich <[EMAIL PROTECTED]> writes:
> I guess one would have to invent a different "print system" for
> that. Perhaps those "error printers" would return a heap allocated
> char string, which the caller(the bison generated parser) is
> responsible for de-allocating.
That'
On Thursday 14 September 2006 12:34, Akim Demaille wrote:
> >>> "Frans" == Frans Englich <[EMAIL PROTECTED]> writes:
> >
> > I'm sure that's practical, but it surely would be cool to be able
> > to craft better messages!
>
> I agree, but there is a real problem: the interface here is outputting
