Versions, dear boy. Versions. Don't forget versions.
We will need them.
(This really belongs on -internals. Reply-to: adjusted)
And while were here, does anyone understand kpathsea? Would it be a
win. I think it would.
<chaim>
>>>>> "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes:
DS> lexer saw a name on the list it'd automagically mark that shared library
DS> for loading.
DS> So if the list had:
DS> localtime|$|@|op|time.so|localtime
DS> perl would know that the localtime function took a scalar, returned a list,
DS> is called like an opcode, and lives in time.so with a name of localtime. If
DS> (and only if) you used localtime, perl would load in time.so for you. In
DS> the optree (or bytecode stream or whatever) perl would have the
DS> I_cant_believe_its_not_an_opcode opcode with a pointer to the function we
DS> loaded in from time.so.
DS> This way it looks like an opcode, talks like an opcode, looks like an
DS> opcode, but isn't an opcode taking up valuable space. (Not to mention
DS> making the optimizer more complex--the fewer the opcodes the easier its
DS> likely to be)
DS> I've got an RFC started on this.
DS> The list would presumably be added to occasionally when a module is installed
--
Chaim Frenkel Nonlinear Knowledge, Inc.
[EMAIL PROTECTED] +1-718-236-0183
