Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] writes: >> I am wanting to restructure Music_element to be more Grob-like. The >> best way to do this, in my opinion, is to create a base class from >> which they both inherit. I have been working on this, but am looking >> for a good name for this base class. Currently I am just calling it >> Propertied_object, but would anyone else be able to come up with a >> better name? > > I have bad experiences with mixing C++ inheritance with GUILE smobs - > the interactions with virtual functions and GC are hairy, and I see > little added value except for collapsing a few functions. Why are you > so keen on changing Music ?
First of all, I made an error in my original post. The object I wanted to modify was Audio_element, not Music_element. Originally, I simply wanted to be able to have properties attached to Audio_elements. More specifically, I want to be able to interact with Audio_elements from scheme code, much the same way as I can interact with grobs. I am seeing Audio_elements as the audio equivalent to the visual grobs. -- Michael Welsh Duggan ([EMAIL PROTECTED]) _______________________________________________ lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
