Dan Sugalski wrote: > >... > > As for threading, well, that's where things get interesting. Perl's tried > it two ways (multiple threads in the same interpreter, and one thread per > interpreter, with cloned interpreters) both of which aren't very good. And > the global lock thing's not that keen either. What is the downside of the global lock on the average single processor machine? I tend to think that the "default" threading model should allow simple and easy, everything-shared multi-threading on ordinary machines. Having a multi-processor-friendly advanced mode is a great extension for the wizards. -- Take a recipe. Leave a recipe. Python Cookbook! http://www.ActiveState.com/pythoncookbook
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4