Ian Hulin <i...@hulin.org.uk> writes: > Hi all, > > The latest git now dies on my V2 Guile system with > .../lily/parse-scm.cc:59:64: error 'scm_local_eval' was not declared in > this scope. > > From Guile V2 NEWS > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > ** No more `local-eval' > > `local-eval' used to exist so that one could evaluate code in the > lexical context of a function. Since there is no way to get the lexical > environment any more, as that concept has no meaning for the compiler, > and a different meaning for the interpreter, we have removed the > function. > > If you think you need `local-eval', you should probably implement your > own metacircular evaluator. It will probably be as fast as Guile's > anyway. > > ----------------------------------------------------------------------- > > This did not crash on Guile V2 until I pulled the latest git > repository today. David, is this part of you ly:export removal or > related parser brain surgery?
Related. #{ ... #} is evaluated in the lexical context of the surrounding function. Is there anything that made Guile a flexible tool left in Guile V2? "compilation" gives us all the disadvantages and rigidity of C at a fraction of its speed, it seems. I'll have to see whether I can come up with something working even half as nicely. Probably will have to be rather close to the kludge we had before. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel