David Kastrup <d...@gnu.org> writes:
> David Kastrup <d...@gnu.org> writes:
>
>> And then there is one thing that is quite non-obvious and needs fixing:
>> a comment.
>>
>> % direction (either #UP or #DOWN)
>>
>> # and $ in comments inside of #{ ... #} are not completely
>> unproblematic. $ was much more dangerous, now both $ and # are a bit
>> more low-profile.
>
> [...]
>
>> With current 2.15, it will start working again if you put a space after
>> #DOWN.
>
> Actually, the comment alone does not faze #(define-... #{ #}) so there
> is something quite more fishy going on. It still works when adding that
> above-mentioned space, however.
>
> I'll have to see what else is up here.
Crapola. The Scheme reader _does_ read the trailing ), but does not
complain. Instead it pushes it back to the port where it is digested
when the _next_ # is coming up.
So yes, I guess it should be possible to fix 2.15.x so that not even the
above comment will give it a hickup. I'll take a look.
--
David Kastrup
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
