At 11:40 AM 9/11/00 -0600, Nathan Torkington wrote:
>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.
This'd also kill require and do, though that's not necessarily a loss in
this sort of environment. Precompiled programs only.
>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.
As would I. I can think of a few ways--the memory usage you get with a
"perl -c" of your program would give you the base eaten by the parsing of
the program. We don't have any good way to judge runtime memory usage,
though the compiled output of perlcc might give an indication of sorts.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
