Digging a little further into the consequences of null_lib_name.patch,
I see trouble ahead if the new library PMC is cloned into another
interpreter.
The fix lets you create a library PMC with no '_lib_name' property,
but src/dynext.c:Parrot_clone_lib_into assumes that every library
PMC has one.
chromatic wrote:
I prefer this patch. It fixes the problem closer to its source. Does it work
for you?
Yes, that works for me. However the fix does not get exercised without
the new test case (or something similar) added in the original patch.
Thanks!
Tom
