Re: precise input location

2005-01-09 Thread Nicolas Sceaux
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] writes: >> Nicolas Sceaux <[EMAIL PROTECTED]> writes: >> >> > Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: >> > >> >> I believe bison has builtin support for handling locations (check out >> >> the bison manual under Locations). May

Re: precise input location

2005-01-09 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > Nicolas Sceaux <[EMAIL PROTECTED]> writes: > > > Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > > > >> I believe bison has builtin support for handling locations (check out > >> the bison manual under Locations). Maybe you could run some experiments > >> whether it's us

Re: precise input location

2005-01-09 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > Nicolas Sceaux <[EMAIL PROTECTED]> writes: > > > Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > > > >> I believe bison has builtin support for handling locations (check out > >> the bison manual under Locations). Maybe you could run some experiments > >> whether it's us

Re: precise input location

2005-01-09 Thread Nicolas Sceaux
Nicolas Sceaux <[EMAIL PROTECTED]> writes: > Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > >> I believe bison has builtin support for handling locations (check out >> the bison manual under Locations). Maybe you could run some experiments >> whether it's usable for us. Here is a patch. The (mode

Re: precise input location

2005-01-09 Thread Nicolas Sceaux
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > I believe bison has builtin support for handling locations (check out > the bison manual under Locations). Maybe you could run some experiments > whether it's usable for us. That was indeed the right direction. I added (first|last)_(line|column)_ slo

Re: precise input location

2005-01-08 Thread Nicolas Sceaux
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > I believe bison has builtin support for handling locations (check out > the bison manual under Locations). Maybe you could run some experiments > whether it's usable for us. Right, thanks. ___ lilypond-d

Re: precise input location

2005-01-08 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > > > > Right now, parser.yy sets the input location of music expressions > > directly (using set_spot()). This method is flawed, since the parser > > occasionally has to look ahead for parsing correctly, thus putting the > >

Re: precise input location

2005-01-08 Thread Nicolas Sceaux
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > > Right now, parser.yy sets the input location of music expressions > directly (using set_spot()). This method is flawed, since the parser > occasionally has to look ahead for parsing correctly, thus putting the > origin property in the wrong spot. If

precise input location

2005-01-03 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > Hello, > > While trying to write a protocol for parsing portions of LilyPond text, > typically for more interactive editing (a quick insert mode that > really works), I encoutered few problems wrt input locations. For > instance: > > [snip] > > I would like to (try to)

precise input location

2005-01-03 Thread Nicolas Sceaux
Hello, While trying to write a protocol for parsing portions of LilyPond text, typically for more interactive editing (a quick insert mode that really works), I encoutered few problems wrt input locations. For instance: guile> (lyp:print-parse-tree (lyp:parse-line "c8.\\f d16 e8 f g2")) [0-17