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 of unprecedented level for what looks like rather immaterial gains), I'd strongly recommend not going there. https://codereview.appspot.com/262980043/ _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
