|
| From: | lilypond |
| Subject: | Re: [Lilypond-auto] Issue 2758 in lilypond: ly_module_lookup caused deprecation warnings when LilyPond running with Guile V2.06 |
| Date: | Wed, 22 Aug 2012 12:31:36 +0000 |
Comment #9 on issue 2758 by address@hidden: ly_module_lookup caused deprecation warnings when LilyPond running with Guile V2.06
http://code.google.com/p/lilypond/issues/detail?id=2758I am worried about the cell count changes of the more straightforward fix, indicating relevant differences in the actually taken actions for a large range of files.
Would it be feasible for a tester to check whether this is connected with noticeable impacts on performance?
Does anybody have a view or idea of the mechanisms or impact of using module-variable? It is, after all, a documented and straightforward interface, so it should be preferable _if_ it does not have significant performance or memory footprints.
| [Prev in Thread] | Current Thread | [Next in Thread] |