Wiz Aus wrote:
Btw, the only other change to the C++ code I had to make is to fix the use of the RTTI to get the class name - the kludge to demunge RTTI typenames is extremely non-portable (and again, very likely to break with future versions of GNU). Again, because you use macros everywhere, it's completely unnecessary - and there's no way that RTTI is faster than managing the storage/retrieval of class names with macros.
You're technically correct, although "very likely to break" is a bit of a misnomer given that it has been working like this for years. I've added a class_name() member to the VIRTUAL_COPY_CONSTRUCTOR macro. But I'm not sure that it covers all cases. In any event, it's used for debugging purposes only.
What/where are the building instructions for Win32? I understand it uses MINGW32, but the source I downloaded certainly doesn't have everything required to build, say, the lilypond-windows executable that comes with the install.
We cross-compile the .exe under Linux. Theoretically, you could build it under cygwin using, but that would be an -ehmm- interesting experience.
-- 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
