Re^11: Shouldn't references be readonly?

This is no answer to my question. My point is: however created, an alias is a reference to something put into a slot of a symbol table entry. I do not see any evidence in your examples against this claim.

UPDATE And then again, a de-referenced reference should behave similar to an alias. AFAICS it does.

Greetings,
-jo

$gryYup$d0ylprbpriprrYpkJl2xyl~rzg??P~5lp2hyl0p$

Comment on Re^11: Shouldn't references be readonly?

Replies are listed 'Best First'.
Re^12: Shouldn't references be readonly? by LanX (Saint) on Aug 05, 2020 at 20:18 UTC
> put into a slot of a symbol table entry. An alias is always a variable true, that's an obvious no-brainer. But typeglob mechanisms are only a part of the way to create them. Especially in `for my $a (@a) { ... }` there is no symbol table entry like you claimed. `my $a` is a private variable and an alias. And newer Perl versions allow activating the feature for refaliasing too, again no symbol table. Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery}	[reply] [d/l] [select]
Re^13: Shouldn't references be readonly? by jo37 (Curate) on Aug 06, 2020 at 07:15 UTC
Accepted. Greetings, -jo `$gryYup$d0ylprbpriprrYpkJl2xyl~rzg??P~5lp2hyl0p$`	[reply]
Re^14: Shouldn't references be readonly? by LanX (Saint) on Aug 07, 2020 at 12:23 UTC
> Accepted How gracious... Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery}	[reply]