> Memory limits we should be able to do, assuming Perl 6 continues to
> have its own malloc.
Well... Perl doesn't use it's own malloc *that* widely. E.g. Linux
doesn't, since at least 5.005_03. FreeBSD doesn't. OpenBSD doesn't.
Darwin doesn't. AIX doesn't. IRIX doesn't. Starting from 5.8.0
Solaris won't (at the behest of Alan Burlison and few others). The
reason? Usually it has been the system malloc being (a) faster (I
think the BSDs) (b) more robust under multithreading (IRIX).
Also starting from 5.8.0 Tru64 or any other naturally 64bitall plaform
won't (since the Perl malloc is not 64bitall-clean).
> CPU usage is a problem... we could provide two similar, but easier to
> implement, features. Throttling (by sticking a tiny little sleep
> between each opcode) and limited running (ie. kill yourself if you run
> longer than X seconds). The latter we might be able to pull of
> externally using SIGALRM, but not all systems have that.
Or setrlimit() for the systems that have that.
> Also things like limiting the number of open filehandles and sockets and
> limiting network usage could be done inside perl.
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dead'. -- Jack Cohen
