According to Jan Dubois:
> For ActivePerl, binary compatibility is even more restrictive: I
> also care about forward compatibility, compiling modules with 5.8.1
> and having them work with 5.8.0.
Then, as you probably realize, you could not have enabled hash seeding
even if this bug had not existed; if you had left it enabled, XS DLLs
would reference at least one new external symbol (PL_hash_seed).
> This won't work if the 5.8.1 headers redefine standard functions as
> macros to new APIs because the dynamic loader will not find those
> when loading into 5.8.0.
So if NO_HASH_SEED is defined, renaming is verboten? OK. In that
case it would be a no-op, so just avoiding it is better anyway.
--
Chip Salzenberg - a.k.a. - <[EMAIL PROTECTED]>
"I wanted to play hopscotch with the impenetrable mystery of existence,
but he stepped in a wormhole and had to go in early." // MST3K
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
