On 06/12/2017 01:00 AM, David Kastrup wrote:
The use case is similar to that of lambda: creating a procedure on the
fly without giving it a name.
Ah, got it. Then makes sense to avoid having to use on-the-fly, by
converting those named on-the-fly procedures into actual markup commands.
Just thinking out loud, but if define-markup-command worked like
define-music-function and friends (i.e. like lambda) so that they
returned a procedure, like this:
command-name = #(define-markup-command (layout props args...) ...
(define command-name (define-markup-command (layout props args...) ...
Rather than the current form:
(define-markup-command (command-name layout props args...) ...
Would that remove the need for on-the-fly or am I missing something?
I'm sure that would not be a trivial change -- again just thinking out loud.
-Paul
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
