in reply to Re^3: Shouldn't references be readonly?
in thread Shouldn't LITERAL references be readonly? (updated)
> compelling reason why they should be read-only.
Again, what is the compelling reason to throw an error with aliased 1 or "string" or undef???
The OP has an example.
Same league, it's not more logical at all.
Probably some implementation detail related to magic edge-cases like auto-vivification or so.
Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^5: Shouldn't references be readonly?
by haj (Priest) on Aug 05, 2020 at 17:58 UTC | |
by LanX (Sage) on Aug 05, 2020 at 18:03 UTC | |
by haj (Priest) on Aug 05, 2020 at 18:43 UTC | |
by LanX (Sage) on Aug 05, 2020 at 18:57 UTC | |
by karlgoethebier (Abbot) on Aug 08, 2020 at 08:28 UTC | |
Re^5: Shouldn't references be readonly?
by jo37 (Chaplain) on Aug 05, 2020 at 18:11 UTC | |
by LanX (Sage) on Aug 05, 2020 at 18:20 UTC | |
by jo37 (Chaplain) on Aug 05, 2020 at 18:40 UTC | |
by LanX (Sage) on Aug 05, 2020 at 18:53 UTC | |
by jo37 (Chaplain) on Aug 05, 2020 at 19:21 UTC | |
|
In Section
Seekers of Perl Wisdom