Additionally, why is the documentation for the lock() keyword split between
perlfunc and threads::shared?
--
Michael G. Schwern <sch...@pobox.com> http://www.pobox.com/~schwern/
Perl Quality Assurance <per...@perl.org> Kwalitee Is Job One
Me? A robot? That's rediculous! For one thing, that doesn't compute at all!
Because lock() is a built-in?
Liz
That would explain why it's in perlfunc, but not why it's in threads::shared
or why one set of docs doesn't reference the other.
If it's a built-in, the docs should be in perlfunc. threads::shared should
simply reference perlfunc.
--
Michael G. Schwern <sch...@pobox.com> http://www.pobox.com/~schwern/
Perl Quality Assurance <per...@perl.org> Kwalitee Is Job One
Fuck with me and I will saw off your legs.
http://www.unamerican.com/
Becuase it's a built-in with no function (other than to provide a hook).
'use threads::shared' uses the hook to make lock() do something specific
to threads; in principle some other 'use' could make lock behave
differently. As to where this should be documented is anyone's guess.
Dave.
--
"Strange women lying in ponds distributing swords is no basis for a system
of government. Supreme executive power derives from a mandate from the
masses, not from some farcical aquatic ceremony."
Dennis - Monty Python and the Holy Grail.