Tom Christiansen writes:
> We've been down this route.  It doesn't help the way you think it does.
> These are merely wafer-thin wrappers about syscalls.  It's Perl's 
> complete infrastructure support system you're seeing, and that you
> will not reduce.

Actually, if we can split compiler from runtime, Apache could choose
to embed only the runtime engine (no eval()s permitted, obviously) with
a corresponding drop in memory consumption.

I don't know how you'd find out what amount of /usr/bin/perl5 is runtime
vs compiletime.  But I'd like to know.

Nat

Reply via email to