Re^3: Postpone garbage collection during a child process run?

[BrowserUk]

(Hate to be the bearer of bad news,

Then just stop!

particularly the BUGS AND LIMITATIONS and the SEE ALSO sections.

• Bugs and limitations amount to:
  • share( <hashref>!<arrayref>) unituatively empties the structure being shared.

    Now fixed by the provision of shared_clone().

  • splice doesn't operate on shared arrays.

    Big deal, not!

  • Taking a ref to a shared structure elements doesn't autovivify.

    Many people wish that Perl didn't autovivify so readily anyway. Again No big deal.

  • refaddr() reports the thread local alias address, not the that of the principle.

    Use IsShared() to obtain a cross-thread usable identifier.

  • each can produce incorrect results when run against nested hashrefs.

    Make a local copy the the hashref and run each on that. Simple.

• See also contains nothing but a list of useful links.

  So why make it sound like it contains a government health warning?

A few limitations, with solutions. No big deal.

And all aimed at someone who didn't mention threads and isn't using them. Stop jumping on bandwagons that you don't understand!

Have you actually written any threaded perl code?

Because your pronouncements on the subject show little or no understanding of the real issues involved.