Re: Debugging/showing internal stuff?

[Nicolas Sceaux]

Le 10 mars 09 à 10:22, David Kastrup a écrit :

> As some sort of progress,
>
> '#{ \notemode { c e g } #}
>
> puts out
>
> (let ((parser-clone (ly:parser-clone parser))) (parse-string-result  
> " \\notemode { c e g } " parser-clone))
>
> but since parser is #f, without quoting one gets
>
> ERROR: In procedure ly:parser-clone:
> ERROR: Wrong type argument in position 1 (expecting Lily_parser): #f
> ABORT: (wrong-type-arg)
>
> Not sure where to go from there.


----- test.ly -----
#(display (current-module))
#(top-repl)
-------------------

==>

#<module 33965d0>
guile> (current-module)
#<directory (guile-user) 22416f0>
guile>

So after invoking (top-repl), we are not the same module as the one
used in the input file. That's why `parser' is not bound to an actual
parser object. In the past (the page that was refered to was written
at the time of LilyPond 2.5), the modules of the input files were named
something like anonymous-ly-module-0, anonymous-ly-module-1, etc, so it
was easy to change to the appropriate module, but that is not the case
anymore: the modules used by input files are not named.

nicolas