Neil Puttock wrote:
As a compromise, how about leaving them in for now, but marking in the documentation as duplicates of \center-align or \left-column and deprecated--users should migrate to the new syntax as the older will eventually go away. As an enhancement, (i.e. more work for developers coming-=>) you could do something like gcc where there's an official idea of deprecation such that the code compiles correctly, but an annoying warning message spits out. Then after a release, in the next development cycle, (or later if that seems kind), they could go away. Of course it would be good if there were a central place to mark deprecations, along with the release in which they were first deprecated, to make later review easier. It would help with the ongoing issue of complaints. If people have missed a whole release cycle before upgrading they'll never see the deprecation warnings, but you can't solve all the worlds problems. Of course, the deprecation list could migrate to a obsolete list, and when coming across something it didn't understand, the parser could check the obsolete list and give a more meaningful message saying to run convert-ly and the last release at which that syntax was valid. It would be a huge help when trying to fix someone else's stuff, built on an old release without a \version.As for \hcenter and \column, should I leave these as duplicates of \center-align and \left-column (which would help minimize user complaints), or remove them? Regards, Patrick |
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
