bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 1356 in lilypond: LilyPond-style comments embedded in a Scheme


From: lilypond
Subject: Re: Issue 1356 in lilypond: LilyPond-style comments embedded in a Scheme expression can't include special characters
Date: Wed, 23 Nov 2011 12:34:58 +0000


Comment #4 on issue 1356 by address@hidden: 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?




reply via email to

[Prev in Thread] Current Thread [Next in Thread]