Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] writes: >> Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: >> > >> > This should not be a big problem. In this case, I solved it by adding >> > begin-of-line-invisible to safe-lily.scm. However, we should probably >> > have some Scheme level macro support for tagging a definition as >> > "safe", ie. >> > >> > (define-safe-public (begin-of-line-invisible .. )) >> >> Something like that could do it: >> >> (define-macro (define-safe-public arglist . body)
> Could you add this? Sorry for not being very reactive since then. I'm about to commit a `define-safe-public' macro, used where appropriate. make web runs fine. >> It would be good also that LY_DEFINE declared as safe the functions >> that it defines, e.g. by invoking declare-safe afterwards: >> >> (define (declare-safe symbol) >> (set! safe-objects (cons (cons symbol (primitive-eval symbol)) >> safe-objects)) >> symbol) >> >> Unless some LY_DEFINEd functions are not safe, in which case >> LY_DEFINE_SAFE should be added. > > Good point. We'll add that to the TODO list. _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
