No such thing as a small change | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Personally I think that I wouldnt use the Readonly module. Partially because what it does is done elsewhere, and i'd be more likely to look there, (Hash::Util for instance would be where i would look for locked hashes). But also because the semantics of readonlyness IMO isnt all that clear. For instance should the readonlyness transfer on assignment? (It doesn't). The other thing that makes me wonder, is why does the module go to such extreme lengths? Making a constant scalar (which seems to me to be a common task mentioned in this list) is pretty easy without it:
Which might not be self documenting, but it solves 99% of the problem domain in a way that doesnt require modules and should work everywhere.
--- $world=~s/war/peace/g In reply to Re: What is the difference between the constant construct in Perl and the Readonly construct in Perl?
by demerphq
|
|