On Sun, 2006-09-17 at 01:20 +0200, Han-Wen Nienhuys wrote:
> Joe Neeman wrote:
> > On Sat, 2006-09-16 at 16:29 +0200, Han-Wen Nienhuys wrote:
> >> Some comments:
> >>
> >> * can you add another macro layer, so __LINE__ and __FILE__ aren't 
> >> sprinkled around in the code? For good measure, you could also add 
> >> __FUNCTION__ .
> > How about something like the attached patch? I "overload" get_property
> > so that it can take a SCM directly. Then I can replace every
> > internal_get_property with get_property.
> 
> Clever! This means that we can do away with the whole internal_FOO 
> business, right? (also for some other functions, I expect.)
> Can you prepare a patch that removes all the internal_XXX  ?

Except that I will need internal_FOO for the scheme hooks. It will be
completely transparent to other parts of the code though (ie.
internal_FOO shouldn't be called directly by anything any more). I
should be able to do something similar for
make_{item,spanner,paper_column} too.




_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to