Re^10: Shouldn't references be readonly? (updated)

Put differently, you want to prevent transformation of references, but using a completely ineffective tool to achieve it. Making references read-only doesn't prevent transformation.

Preventing transformation (stringification, numification, but not booleanification) of references might be a good idea.

Issues:

Intentional uses of $ref+0 would have to be replaced by refaddr($ref).
Intentional uses of "$ref" would have to be replaced.
Programs that mostly function will start dying instead.

Benefits:

Catch some bad code (But what code wouldn't already be obviously wrong?)

Comment on Re^10: Shouldn't references be readonly? (updated) Select or Download Code

Replies are listed 'Best First'.
Re^11: Shouldn't references be readonly? (updated) by Corion (Patriarch) on Aug 10, 2020 at 06:08 UTC
See also stringification, which allows you to say: `no stringification;` [download] and forbids `"$ref" # stringify $ref . "foo" # concat lc $ref lcfirst $ref uc $ref ucfirst $ref quotemeta $ref` [download]	[reply] [d/l] [select]
Re^12: Shouldn't references be readonly? (updated) by ikegami (Patriarch) on Aug 11, 2020 at 10:39 UTC
noice. There are only dev releases of the module. If this is something you (the reader) is interested in, perhaps you could contact the author to encourage a proper release or assist with it.	[reply]
Re^13:Shouldn't references be readonly? (updated) by LanX (Saint) on Aug 11, 2020 at 15:13 UTC
> noice := nice noise? ;-) Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery}	[reply]