in reply to Re^2: passing shared blessed object part 2
in thread passing shared blessed object part 2

I believe that the newer versions of threads::shared override bless in order to enable the new shared blessed refs facility. And whilst I have no direct knowledge that it does, it wouldn't surprise me if Moose or Class::MOP did the same thing for their own purposes. That could well account for (at least some) of the errors you see when you include both.

Nope, Moose/MOP does not (and never will) override global behavior like that. The fact that threads::shared does means that might be the source of the problem right there.

-stvn
  • Comment on Re^3: passing shared blessed object part 2

Replies are listed 'Best First'.
Re^4: passing shared blessed object part 2
by BrowserUk (Patriarch) on Nov 25, 2009 at 02:07 UTC
    Nope, Moose/MOP does not (and never will) override global behavior like that.

    Fair dos. I only said it was a possibility for the cause of the conflict.

    It'd be interesting to see if Moose can interoperate with threads::shared in a sane fashion. I hope that the discussion (and the solution found if any), doesn't disappear into the IRC bitbucket along with so much other potentially useful wisdom.

    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]

In Section Seekers of Perl Wisdom