That's overengineering in my opinion. GUILE's own header macros take
all the given parameters so we get a discrepancy when LilyPond's
equivalents don't do so.
Unless there is a very compelling reason to indulge in this sort of
thing (and the template pokery-trickery in lily-guile-macros.hh is
Reviewers: ,
Description:
The compiler is capable of counting the number of arguments in a
callback. It can also check that the number of optional arguments does
not exceed the total number of arguments.
I've put the code that accomplishes these things in
lily-guile-macros.hh, but it is
