Re^2: Modification of a read-only value attempted

You will notice when you try to write to the constant, which I suppose is the point of it :) That said, I do prefer Readonly as well because it allows for completely normal-looking "non-variables". Having to remember to dereference anything that's supposed to be a constant doesn't make sense except as an idiosyncrasy of the language. What's more, Readonly also lets you write-protect hashes and arrays although at a performance cost.

Comment on Re^2: Modification of a read-only value attempted

Replies are listed 'Best First'.
Re^3: Modification of a read-only value attempted by BillKSmith (Monsignor) on Nov 27, 2012 at 20:50 UTC
This discussion reminds me of a related question. When a Readonly hash or array contains references, are the targets of those references protected? As a common example, are the elements of Readonly matrix protected? Bill	[reply]
Re^4: Modification of a read-only value attempted by AnomalousMonk (Archbishop) on Nov 27, 2012 at 21:23 UTC
Easy to test: `>perl -wMstrict -MData::Dump -le "use Readonly; ;; Readonly my %h => (a => {b => {c => {d => 1}}}); dd \%h; ;; $h{a}{b}{d} = 2; " { # tied Readonly::Hash a => { # tied Readonly::Hash b => { # tied Readonly::Hash c => { # tied Readonly::Hash d => 1, }, }, }, } Modification of a read-only value attempted at -e line 1` [download] See also DESCRIPTION section of Readonly.	[reply] [d/l]