Marc Hohl <m...@hohlart.de> writes: > Am 01.10.2012 11:00, schrieb d...@gnu.org: >> >> Or define-session-public. define-session will be for data that is reset >> per session, but not publicly accessible. Which is probably what you >> want if all the accessor functions are already in your .scm file. > I think that -public is needed for data to be accessible for a user? > Or is it sufficient that the function accessing the data is -public?
"public" just publishes the variable binding. The binding does not need to get published to be accessible to functions in the same source file: the binding is only needed when the functions referring to it are _defined_, not when they are being used. Of course, you can't do session management on a variable you can't even access, but publishing the variable for everybody else to tamper with is not going to make our problem smaller. So we need to be able to do session-management on the variable _without_ publishing it, and that means in the module where it is being defined. And the easiest way is to have separate defining commands for that purpose. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
