Werner LEMBERG <w...@gnu.org> writes: >>> However, I can live with "violin1" or "violin1part3" also. >> >> "part" would be a more like a tag of a struct or index of an >> associative array, so \violin1part3 could access something >> corresponding to violin[1].part[3] in C-speak when defined properly. > > Actually, it would be rather > > part[3].violin[1]
That's the logic of the musician rather than the programmer speaking. If you wanted it to be _that_, you'd have to call it \part3violin1, I am afraid. > and I would welcome such a possibility to add more structure. I actually don't see all that many uses for it (possibly because I did not write large projects in Lilypond yet) until one starts doing iterators and similar fun (not part of this proposal). One obvious use case would be to use a vector as the recipient for \parallelMusic. -- David Kastrup _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
