>>>>> "jac" == James A Crippen <[EMAIL PROTECTED]> writes:
jac> Using MP:PROCESS-YIELD you could probably implement your own jac> preemptive threading system inside CMUCL but it would be a lot of work jac> that might be better spent on other tasks (like making preemptive OS jac> threads work in CMUCL). CMUCL's multiprocessing already has a preemptive scheduler; it can be enabled via MP::START-SIGALRM-YIELD. I wouldn't recommend using it, however, as it's interrupt-driven, and parts of the CMUCL code base are not interrupt-safe. jac> The difference between threads and processes is ostensibly that jac> threads are lighter-weight than processes, ie that switching jac> threads is cheaper than switching processes. the real difference between a thread and a process is that threads belonging to the same task share the same address space, whereas each process has its own separate address space. -- Eric Marsden <URL:http://www.laas.fr/~emarsden/>
