Guile-2 and define*-public with curried functions

[Paul Morris]

> 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