Re: Issue 1826 in lilypond: Guile 2.0 compat: `conditional-circle-markup' definition needs to be relocated

[lilypond]

Comment #4 on issue 1826 by address@hidden: Guile 2.0 compat:  
`conditional-circle-markup' definition needs to be relocated
http://code.google.com/p/lilypond/issues/detail?id=1826

Re comment 2:
Hi Reinhold,
Things are a bit more complicated in Guile V2.0, because now you can be  
loading a scheme file in slightly differing environments:
1. File is loading as part of another load operation (e.g. loading  
markup.scm as part of loading lily.scm).
2. Evaluating (Interpreting code) in a guile statement which then kicks off  
a load operation.
3. Byte-compiling code containing a guile statement which kicks off a load  
operation.

In V1, because it is purely and simply an interpreter, (load) generally  
implies doing a combination of (1) and (2): i.e. load up the scheme file  
and interpret it straightaway. Because of this this I think there was a  
possibility of forward-referencing within a file, although I have never  
successfully done this from the Guile REPL.  However, because of (3), Guile  
V2 has had to tighten up on the kind of lazy binding that allowed this.

In 1349 I split up the load list in lily.scm into subsections to allow  
clean separation of definitions on which other definitions depended to be  
loaded early, hence define-markup-macros.scm.

If you're seriously disturbed by Patrick's suggestion in his patch, it  
could go into its own define-fretboard-markup-macros.scm, to be loaded  
after define-markup-macros in the list.

Another possibility is to get all the scheme files generating the markup  
sub-language to generate a separate scheme module (lily markup) ? (scm  
markup) ?

What are your feelings on either of these propositions?  Let me know and  
I'll get working on a patch for this.

Ian