Re: RFC 155 - Remove geometric functions from core

[Nick Ing-Simmons]

Tom Christiansen <[EMAIL PROTECTED]> writes:
>
>Disastrously, you will then also lose the shared text component,
>which is what makes all this cheap when Perl loads.  

But we can on modern OSes have shared data too.

>Since the
>modules will have to be pasted in the data segment of each process
>that wants them, they aren't going to be in a shared region, except
>perhaps for some of the non-perl parts of them on certain architectures.
>But certainly the Perl parts are *NEVER* shared.  That's why the
>whole CGI.pm or IO::whatever.pm stuff hurts so badly: you run with
>10 copies of Perl on your system (as many people do, if not much
>more than that), then you have to load them, from disk, into each
>process that wants them, and eth result of what you've loaded cannot
>be shared, since you loaded and compiled source code into non-shared
>parse trees.  This is completely abysmal.  Loading bytecode is no win:
>it's not shared text.

Loading perl5 bytecode is a non-win I agree 110%.

But if perl6 bytecode does not need to be modified to be used
it can be mmap()'ed shared, read-only and hence page-cached and reused.

-- 
Nick Ing-Simmons