I'd put all delayable code into the __DATA__ section, and provide each package with its start and end offsets into the __DATA__ section, in a hash table (initially written with enough whitespace for the values as placeholder for yet unknown offsets).
That way an AUTOLOAD subroutine would seek to that point, read the appropriate amount of bytes, eval them and goto the just compiled sub or method.
--shmem
_($_=" "x(1<<5)."?\n".q·/)Oo. G°\ /
/\_¯/(q /
---------------------------- \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}
In reply to Re: Bootstrapping and cleaning after remote execution of method in framework consisting of multiple modules
by shmem
in thread Bootstrapping and cleaning after remote execution of method in framework consisting of multiple modules
by mman
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |