Wiz Aus wrote:
Ok, now I'm trying to actually play with the lilypond code -- but it seems to be full of completely illegal C++ - like trying to cast class member functions to standalone functions etc. etc. The cases I've found so far are all very easy to fix, just by adding proxy function definitions in the macros that set these things up, so I can't work out why it would be written like this in the first place.
Because we want to skip the (proxy) function calls for performance reasons.
Has anyone ever tried to get the code compiling on another C++ compiler?
No, and it has never been our intention to support other compilers. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
