| 1 |
root |
1.1 |
Should cvcache be per CV (keyed by thread) or per thread (keyed by CV)? |
| 2 |
|
|
|
| 3 |
|
|
Maybe ought to protect all SVs by a mutex for SvREFCNT_{dec,inc}, |
| 4 |
|
|
upgrades and so on. Then use SvMUTEX instead of CvMUTEX for CVs. |
| 5 |
|
|
On the other hand, people shouldn't expect concurrent operations |
| 6 |
|
|
on non-lexicals to be safe anyway. |
| 7 |
|
|
|
| 8 |
|
|
Probably don't need to bother keeping track of CvOWNER on clones. |
| 9 |
|
|
|
| 10 |
|
|
Either @_ needs to be made lexical or other arrangments need to be |
| 11 |
|
|
made so that some globs (or just *_) are per-thread. |
| 12 |
|
|
|
| 13 |
|
|
tokenbuf and buf probably ought to be global protected by a global lock. |
