On Sun, Mar 22, 2020 at 10:09 PM David Kastrup wrote:
> > In the code below, it looks like only one of the two definitions in
> > the body of my-macro-new takes effect. Is this expected, and if so,
> > why?
> >
> > (defmacro-public my-macro-old (command-and-args . definition)
> >
Han-Wen Nienhuys writes:
> Hi there,
>
> in my quest to get lilypond working with GUILE 2+, I've hit another
> stumbling block.
>
> In order to make compilation with GUILE 2+ working, we have to move
> away from runtime symbol definition (ie. module-define! calls).
>
> In the code below, it
On 3/22/20 12:07 PM, Han-Wen Nienhuys wrote:
Hi there,
in my quest to get lilypond working with GUILE 2+, I've hit another
stumbling block.
In order to make compilation with GUILE 2+ working, we have to move
away from runtime symbol definition (ie. module-define! calls).
In the code below, it
Hi there,
in my quest to get lilypond working with GUILE 2+, I've hit another
stumbling block.
In order to make compilation with GUILE 2+ working, we have to move
away from runtime symbol definition (ie. module-define! calls).
In the code below, it looks like only one of the two definitions in
