MOON
Server: Apache/2.2.21 (Unix) mod_ssl/2.2.21 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4
System: Linux vps.panamaemb.org.sg 3.10.0-1160.80.1.vz7.191.4 #1 SMP Thu Dec 15 20:31:06 MSK 2022 x86_64
User: panama (500)
PHP: 5.2.17
Disabled: NONE
Upload Files
File: //proc/2/cwd/installd/perl588installer/perl-5.8.8/ext/Thread/Notes
Should cvcache be per CV (keyed by thread) or per thread (keyed by CV)?

Maybe ought to protect all SVs by a mutex for SvREFCNT_{dec,inc},
upgrades and so on. Then use SvMUTEX instead of CvMUTEX for CVs.
On the other hand, people shouldn't expect concurrent operations
on non-lexicals to be safe anyway.

Probably don't need to bother keeping track of CvOWNER on clones.

Either @_ needs to be made lexical or other arrangments need to be
made so that some globs (or just *_) are per-thread.

tokenbuf and buf probably ought to be global protected by a global lock.