Nicholas Clark <[EMAIL PROTECTED]> wrote: > I'm trying to understand how morph works. perlscalar's morph looks like this:
[ broken code ] > I think that there are 2 bugs here At least, yes. The better and general morph code is pmc.c:pmc_reuse(). > 2: The code isn't thread safe, even though it thinks that it is: > I see no write barrier. There's no reason why on a dual CPU machine the > parallel reader doesn't see the writes to memory in the order: Yep. > Nicholas Clark leo
