Re: Indirect Object Syntax

and because Perl's interpreter could potentially get this wrong, so could any human trying to understand the code.

I think it is less about people understanding the intent of the author, and more about having newer Perl users get frustrated when a syntax that worked in one part of the code doesn't work in a different part of the code. Perl has several of these problems, and we can eliminate one of them by giving up on the indirect method syntax.

An example of another ambiguity is when you want to generate multiple elements per iteration of "map".

%set= map { $_ => foo($_) } @list;
%set= map +( $_ => foo($_) ), @list;
[download]

The first syntax is more idiomatic and looks better, but sometimes (depending on the code in the block and maybe also what comes after it) perl will decide that the block was a hashref notation and give you a nonsense error message. I've started always using the second notation just because it never parses incorrectly. This is *not* a universal recommendation, just a personal preference.

Comment on Re: Indirect Object Syntax Download Code

Replies are listed 'Best First'.
Re^2: Indirect Object Syntax by LanX (Saint) on Nov 07, 2021 at 09:16 UTC
> I've started always using the second notation just because it never parses incorrectly. I'd rather go for extra semicolon: `%set= map {; $_ => foo($_) } @list;` demo with `perl -de0` `DB<45> x map {a=>1} 1..3; # seeing hash, but co +mma missing syntax error at (eval 55)[c:/Strawberry/perl/lib/perl5db.pl:738] line +2, near "} 1" DB<46> x map {a=>1}, 1..3; # seeing hash again 0 HASH(0x2f501e8) 'a' => 1 1 HASH(0x2f4a1e8) 'a' => 1 2 HASH(0x2f4d0e0) 'a' => 1 DB<47> x map {;a=>1} 1..3; # seeing code 0 'a' 1 1 2 'a' 3 1 4 'a' 5 1 DB<48>` [download] YMMV! :) edit Anyway, Perl should check for the missing comma. I suppose this happens too late for the parser. Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery}	[reply] [d/l] [select]
Re^3: Indirect Object Syntax by choroba (Cardinal) on Nov 07, 2021 at 21:50 UTC
> Anyway, Perl should check for the missing comma. I suppose this happens too late for the parser. IIRC, the parser can only check the following token when deciding whether the { starts a block or an anonymous hash. That's also why the ; helps. `map{substr$_->[0],$_->[1]\|\|0,1}[\\|\|{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^ARGV,3]`	[reply] [d/l]
Re^4: Indirect Object Syntax by LanX (Saint) on Nov 08, 2021 at 00:00 UTC
yeah, that's what I meant with > I suppose this° happens too late for the parser. °) i.e. the comma edit Anyway: any correctly parsed LIST inside an `{anonymous hash}` is also a legal block (just the LIST returned) Perl could always try to parse a block and look if there is a comma following. Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery}	[reply] [d/l]


go ahead... be a heretic
	PerlMonks

Re: Indirect Object Syntax

demo with perl -de0

edit

edit

demo with `perl -de0`