At 11:23 AM -0400 6/12/02, Melvin Smith wrote:
>At 04:55 AM 6/12/2002 -0400, Dan Sugalski wrote:
>> loadlib Sx, Sy
>>
>>Where Sx is the fully qualified name of the library we're loading,
>>and Sy is the name of the routine that we're invoking once we load
>>the library. This should be the *only* routine the library exports.
>>
>>The exported name should be the MD5 checksum of a string that
>>represents the actual routine name we're looking for. This, I
>>think, should be specified somewhere external to the library, in
>>some sort of metadata file, I think. (Not sure, I'm waffling here.
>>But we need this to be unique)
>
>What is MD5 checksum buying us over a sufficiently mangled name?
>We are only worried about uniquness, right? I was hoping we could do
>extensions without needing a pre-processor to get away from the current XS
>mess. Why not something plain-text like:
It's length, too. We need to keep the name under 32 characters. If
we're wedging module/author/version into the name (for extension it's
reasonable) it's tough to keep them under that limit. Easier to not
bother and just MD5 the thing by default. OTOH, we can set this as a
standard and, if we use metadata, read the real name from the
metadata file. Which might be something shorter, you never know.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
