>>>>> "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes:
DS> That strikes me as very much too high level a thing. I'm figuring there
DS> will be no more than one file, and we may well go so far as to weld the
DS> processed version of it into a shareable library that gets loaded in as
DS> part of perl's startup.
i second that direction. this is for perl core functions and not for
user level stuff. it makes it possible to define built in functions that
do get loaded dynamically without any use statements. the table just
needs to map the predefined function names and that map is fixed at
install time (or maybe some module installs can update and rebuild it).
DS> Loading this file *must* be fast. If it's not fast, we're not
DS> doing it. (I don't want to spend 10-20msec per perl activation
DS> just because it's decided to make this file perl code that gets
DS> found and interpreted every time...)
i like that too. this is more an internals thing as it really doesn't
affect the language. we can make it modifiable by the user but it will
always need to be rebuilt in to the .so.
this is simple, fast and meant for dynamic loading of perl core
stuff. it is not for autoloading of user level modules. that should be
left to a module like schwern's.
uri
--
Uri Guttman --------- [EMAIL PROTECTED] ---------- http://www.sysarch.com
SYStems ARCHitecture, Software Engineering, Perl, Internet, UNIX Consulting
The Perl Books Page ----------- http://www.sysarch.com/cgi-bin/perl_books
The Best Search Engine on the Net ---------- http://www.northernlight.com
