Comment #7 on issue 4357 by [email protected]: Patch: Redesign listeners using
templates
https://code.google.com/p/lilypond/issues/detail?id=4357
Yes, sorry. Stupid naming conflict from the "cosmetic change" that I was
sure I had tested. The really stupid thing is that come next change, the
whole conflicting function will be gone anyway. So I need to resolve this
conflict for the sake of a few days. But the next change does not fit
without problems without further infrastructure changes and warrants
independent review anyway. So I don't want to pile on everything on this
issue, or review becomes infeasible.
So at any rate I don't want to hear any proposals for
naming "tlr_get_listener" (which I have placed in the next fix I'll load up
in a few minutes, with tlr being short for translator_listener_record)
differently. It won't be round long enough to matter.
I'd have sent this hours ago but then I got into a real git-rebase mess.
Should have shaken it out now.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
