Re: Using \global - Lilypond 2.9.20 Windows

[Han-Wen Nienhuys]

Erik Sandberg schreef:
> On Tuesday 10 October 2006 17:58, Han-Wen Nienhuys wrote:
> > Erik Sandberg schreef:
> > > > Yes, I think that's a good idea.
> > > The attached patch fixes this and various other fixes:
> > > - add equal_p for Input and Prob
> > > - ASSIGN_EVENT_ONCE checks for inequality before warning.
> > > - musics generated by parser always have their origin set.
> > > - document-music.scm uses the auto-generated event classes
> > > - small cleanup in translator's macro trickery
> > >
> > >
> > > The 'types music property is now only used by music functions AFAIK;
> > > perhaps we should deprecate it soon.
> > Yes, while you're at it, the accepted argument of the ADD_TRANSLATOR
> > macro should also go (global search & replace patch).
>
> Should I remove the second unused arg of DECLARE_*SMOBS as well?

Yes, go ahead.


> > I think it's better to name it as a library function:
> >
> >   ly:studly-caps->lisp-identifier
> >
> > taking strings, and use that.
>
> ok, done. I called it ly:camel-case->lisp-identifier, (camel case is the term 
> that Wikipedia prefers). The function remains in music-scheme.cc, because 
> it's only used for music so far, and I didn't find a spot for generic 
> string-handling functions.

general-scheme.cc ?

--

Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen

LilyPond Software Design
 -- Code for Music Notation
http://www.lilypond-design.com