Hi Charles, > My intention is definitely not to create a representation where the notes and > semantics cannot be passed together into different contexts
Good! That’s important. It’s also likely critical (as David brought up) to either completely disallow the entry of notes and semantics which differ, or at least have a well-considered and -documented mechanism for how to handle the inevitable situation where notes and semantics differ. > I was just trying to make a point that it makes sense to keep the information > separate within EventChord. In terms of representation, I agree… But let’s remember that David has an *immense* grasp of Lilypond’s current (and, to some extent, future/possible) workings — arguably more than anyone, including the founding developers — so I would suggest getting his OK on whatever structure/mechanism you end up with. > even though they will be separate entries in EventChord, that doesn't stop > the possibility of using them together, does it? No, as long as the “note-semantic difference” issue has been addressed. Thanks! Kieren. ________________________________ Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: [email protected] _______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
