On Wednesday 05 October 2005 08.10, Wiz Aus wrote: > Managed to get all the lilypond code to at least *compile* now, although a > long way off linking and running! > > All this does is ensure that member functions aren't stored directly as > standalone function pointers - it creates a thunk or proxy function to call > the member function and then stores that. > The thunks get created whether they're needed or not, but maybe a really > good compiler would optimization them out (doubtful). > I do have to ask though - why on earth not do these as regular virtual > functions??
I think it's related to efficiency. I think those functions were added during a massive optimization. Anyway, you haven't mentioned which compiler you're using, and which commands you've used for building. If you aren't using GCC, then that's probably the problem. -- Erik _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond