"Thomas F. Burdick" <[EMAIL PROTECTED]> writes: > So what's your issue with inserting yeilds in the computational code? > If it's just an issue of preferring not to ... well, that's not an > option with CMUCL, unless you want to deal with the hazards of the > SIGALRM scheduler. You can always use macrology to make two versions > of your code: one that yeilds, for better interactivity; and one that > doesn't, so as not to waste cycles when you're planning on leaving the > machine.
Indeed, I'm considering the option of inserting yields. Yet, I have not done such a thing before, and cannot estimate how much it will disturb the rest of the code. Thus, I would prefer an automatic way. Nicolas. P.S.: Process-yield appears to be rather fast, so I guess I could do without macrology.
