I'd like to poke around with Python's compiler module and look at the AST--you could enforce that a certain class of functions have no side effects, and then spawn multiple processes to execute them semi magically.
Futures like the ones in IO (http://www.iolanguage.com/scm/git/checkout/Io/docs/IoGuide.h...) always struck me as a pretty cool way to abstract away synchronization problems. Using the multiprocess stuff as a background would be fun.
There's probably a whole bunch of other Enumerable methods that could be made to run in parallel as well.
It's multicore if you're using jruby.
async {
do_something;
cede;
do_something;
}
do_something_else;
cede;
See http://search.cpan.org/dist/Coro/Coro.pm for more information.[Edit: If you want to see a continuation-based web framework built with Coro, look at Continuity: http://search.cpan.org/~awwaiid/Continuity-0.994/lib/Continu...
It's very cool.]
Have you heard of Stackless Python? That might be what you are looking for. http://www.stackless.com/
Finally, Ruby has more than one implementation. Finding a hole in one implementation says nothing about the language overall.
It has.
(That's the only vulnerability ever found in qmail, and it wasn't exploitable --- Postfix has had much worse).
The point is that writing simple software in C is possible. But writing complex software is very very hard.
If you took a class with Bernstein, you might be familiar with the ISP whose entire mail operation, including customer POP and virtual hosting, I ran on qmail --- that'd be EnterAct. So yeah, I'm not buying your "qmail is too simple to matter" argument. If you want to chase it down, I'll be happy to show you where the last few Sendmail vulnerabilities were found. Clue: not in the crazy Sendmail features that qmail lacks.
But that's besides the point. You didn't answer my question.
Name a piece of code of comparable complexity to qmail that's never had an integer overflow. Here's another hint: Perl isn't one of them.