On 2008/10/03 18:42 -0700, sdfgsdhdshd wrote: > Han-Wen Nienhuys-5 wrote: > > One tricky aspect is that the GUILE evaluator is fundamentally broken: > > it rewrites Scheme expressions for memoization in thread-unsafe ways > > all over the place. > > > > For Lily itself, I think it will also be very tricky: evaluating grob > > properties through callbacks is assumes that there is only one > > evaluation going on at the same time. > > > > You mean there must be only one .ly file on the command-line?
No, we were talking about the possibility of parallelizing code to take advantage of multi-core CPUs to process _one_ file at the same time, but you can of course take advantage of a multicore CPU if you process several ly files at the same time with lilypond -djob-count=NUMBER LY_FILES -- John _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
