On Wed, May 30, 2012 at 1:08 AM, David Kastrup <d...@gnu.org> wrote: > Han-Wen Nienhuys <hanw...@gmail.com> writes: > >> As a consequence, GUILE is not only the language for writing >> extensions, but it is the entire platform upon which LilyPond is built >> internally too: almost every C++ data structure is manipulated and >> passed on as a SCM variable as well, and there is little prospect of >> ever being able to separate them. >> >> If I would re-do it, I would do so in a language where you can write >> have the data be inside native classes, and automate generating >> methods (setters, getters) and hooks (property callbacks), such that >> the core program wouldn't need to be aware of the scripting language. > > You mean, use Goops?
It would have to be compiled too, for type checking. It would have to be actively maintained too; this was another grave error in choosing GUILE. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
