On Tue, 2015-04-14 at 10:25 +0200, Andreas Schneider wrote: > Am 14.04.2015 um 10:19 schrieb Richard Shann: > > I could be of more help if you decide to go with generating a scheme > > script as I have done this fairly recently. I didn't write the denemo > > xml format so I know less about it - besides some obsolete forms it has > > an overly-sophisticated method of giving staffs and voices id's and then > > looking them up later. It is a more abstract way of describing the > > Denemo music data which would be appropriate if there were ambitions for > > the denemo format to be used by other programs. > > Using the scheme script to build the music will be more robust as the > > rule is never to change the semantics of a Denemo scheme procedure - we > > just create a new one, while the .denemo format does evolve slowly. > > > > So practicality and elegance are negatively correlated between the three > > methods we have come up with! > > I see. Without having any knowledge about Denemo's internals, I would > surmise that for each built-in Scheme command there is a C function that > imlements it. Is that true? And if yes, can I use those C functions > directly? That would be a fourth, more elegant way.
but those functions take parameters of the opaque type SCM which are created by Guile, the Scheme interpreter we use and return SCM values... Richard > > Andreas > > > _______________________________________________ > Denemo-devel mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/denemo-devel _______________________________________________ Denemo-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/denemo-devel
