> Well, I'm a huge Python fan myself, but multiprocessing is not really > a solution as much as it is a workaround. Python as a language has no > problem with multithreading and multicore support and has all > primitives to do conventional shared-state parallelism. However, the > most popular /implementation/ of Python sacrifies this for > performance, it has nothing to do with the language itself.
Actually, no. Neither Python nor Ruby can utilize more than a single processor using threads. The only way to use more than one processor is with processes. -- Bruce Eckel _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe