On Oct 27, 2004, at 6:24 AM, Gisle Aas wrote:
How about the code JITed from the bytecodes. Will it be shared?
The JITed code can't be shared directly--in it's current form, it
(intentionally) includes absolute addresses which wouldn't be valid for
other processes.
But the exec core allows (or, w
At 6:24 AM -0700 10/27/04, Gisle Aas wrote:
Dan Sugalski <[EMAIL PROTECTED]> writes:
Bytecode files on-disk are
shared across all the processes in the system, so you only get one
in-memory copy of a file, which saves both RAM and load time if you're
u
Dan Sugalski <[EMAIL PROTECTED]> writes:
> Bytecode files on-disk are
> shared across all the processes in the system, so you only get one
> in-memory copy of a file, which saves both RAM and load time if you're
> using a file that another process is usi
Dan Sugalski wrote:
At 12:00 PM +0100 10/27/04, Peter Hickman wrote:
Presently Python compiles it's py files to pyc files that can then be
run without access to the source (the py).
Would Perl 6 be able to do this? Compile the pl to plc and pm to pmc
and load the ??c version if it was available
At 12:00 PM +0100 10/27/04, Peter Hickman wrote:
Presently Python compiles it's py files to pyc files that can then
be run without access to the source (the py).
Would Perl 6 be able to do this? Compile the pl to plc and pm to pmc
and load the ??c version if it was available and newer than the
On Wed, Oct 27, 2004 at 12:00:33PM +0100, Peter Hickman wrote:
> Presently Python compiles it's py files to pyc files that can then be
> run without access to the source (the py).
>
> Would Perl 6 be able to do this? Compile the pl to plc and pm to pmc and
> load the ??c version if it was availa
