Bug#1020511: perl-doc: threads::shared(3perl) man page is unclear on when a lock on a variable is needed

[Vincent Lefevre]

Package: perl-doc
Version: 5.34.0-5
Severity: normal

In general in locking mechanisms, one has read locks and write locks,
but the threads::shared(3perl) describes only a single kind of lock.
So is locking necessary for any kind of access? Or only when there is
a possibility of an explicit write by some thread? Or only for write
accesses (but I doubt that they are atomic, so that they should also
affect read accesses)?

And isn't there a way to differentiate read locks and write locks?

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 5.19.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages perl-doc depends on:
ii  perl  5.34.0-5

perl-doc recommends no packages.

Versions of packages perl-doc suggests:
ii  groff-base            1.22.4-8
ii  man-db [man-browser]  2.10.2-3

-- no debconf information

-- 
Vincent Lefèvre <vincent at vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)