Re: Ideas On what a SV is

[Chaim Frenkel]

 "DS" == Dan Sugalski [EMAIL PROTECTED] writes:

DS At 10:26 PM 8/12/00 -0400, Chaim Frenkel wrote:
 If we are going to have pre-compiled modules (bytecode or machine) why
 bother with AUTOLOAD?
 
 The "registry" would handle the 'autoloading'

DS It can't, though. We don't know at compile time (especially if we're 
DS compiling just a module) what AUTOLOAD could be called with.

Sorry, What I meant was, the need for AUTOLOAD went down. Pulling in
modules as needed, for speed reasons.

If items are loaded on demand (socket, dbm, http, whatever) so can
arbitrary pieces of code.

Blue Sky

All compiled code is in a special file that allows mmap access.[1] Then
an unrecognized subroutine, can be checked against the registry. And
an automagical use can be performed.

/Blue Sky

Actually that's a little too automagical, it might make typos turn into
wierd calls.

chaim


[1] I'm remembering my MVS days with all code in PDS with the compiled 
code arranged on disk to quickly load itself into memory.

chaim
-- 
Chaim FrenkelNonlinear Knowledge, Inc.
[EMAIL PROTECTED]   +1-718-236-0183

Re: Ideas On what a SV is

[Dave Storrs]

On Fri, 11 Aug 2000, David L. Nicol wrote:

[...]
 Redefining a method during run time --- is that even a feature that
 needs to be supported?

I think so.  A couple of examples are the Memoize module, which
works by rewriting your memoized function into something that uses
caching, then replacing the old version with the new version in the stash.

Another time you would want to do this would be the following: you
write your AUTOLOAD function such that, when it receives a request it can
handle, it creates a sub to handle the request and installs the sub 
directly in the stash so that, the next time you need that function, you
don't need to traverse @ISA before going to AUTOLOAD.

Dave