Comment #4 on issue 1356 by d...@gnu.org: LilyPond-style comments embedded
in a Scheme expression can't include special characters
http://code.google.com/p/lilypond/issues/detail?id=1356
Update, update, read all about it...
Currently #{ ... #} is implemented by reading the contents without any
attempt of tokenization and/or interpretation, but employing the Lisp
reader for reading after $ and #. There had been a brief period of time
where the above actually would have worked. However, the last commit for
GuileV2 compatibility has reintroduced the dependency of cursory parsing of
# and $ at compile time, and replacement at runtime.
One approach for improving behavior again would be to not just record the
thunks for # and $ at compile time, but also their source position and/or
source expression, and just discard unused expressions. You could not
expect to place unbalanced Scheme code in comments or strings like #{ "$(no
closing paren" #} but the situation would still be improved.
How relevant is this problem in practice?
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
