[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Guile-2 and define*-public with curried functions
From: |
Paul Morris |
Subject: |
Guile-2 and define*-public with curried functions |
Date: |
Sun, 8 Nov 2015 11:49:49 -0500 |
> On Nov 8, 2015, at 9:22 AM, address@hidden wrote:
>
> As a note aside, define*-public with curryied functions is broken in
> Guile-2 and needs to get split into define* and export separately.
Hmmm… this sounds like it might be a relatively straightforward and
well-defined way to help with the Guile-2 work. Is that the case? Am I
understanding it right that the idea is to avoid using define*-public with
curried functions in the LilyPond codebase (but split these cases into separate
define* and export steps)?
-Paul
- Guile-2 and define*-public with curried functions,
Paul Morris <=