Re: I use postfix dereferencing ...

in reply to I use postfix dereferencing ...

This seems like utter madness.

In what world is $aref->@* clearer than @{ $aref }?

Maybe I'm getting old but I'm not seeing the benefit here.

Three thousand years of beautiful tradition, from Moses to Sandy Koufax, you're god damn right I'm living in the fucking past

Comment on Re: I use postfix dereferencing ... Select or Download Code

Replies are listed 'Best First'.
Re^2: I use postfix dereferencing ... by Eily (Monsignor) on Feb 06, 2019 at 15:38 UTC
You could even just write @$aref in your example. Post deref can be more useful with more complex expressions like: `$myobj->onemethod()->{blue}->anothermethod()->[4]->@*` where you can read the thing in the order in which they happen (call onemethod, get the value at "blue", call anothermethod, get the value at 4, then deref), rather than `@{ $myobj->onemethod()->{blue}->anothermethod()->[4] }` where you read the steps from left to right, and the last one back on the left. I'd use a temp variable in both cases though. Postderef can also help with slices where `$some->{nested}{$complex{struct}}->@{qw<where I want more than one value>}` is easier to read than `@{$some->{nested}{$complex{struct}}}{qw<where I want more than one value>}`. Again a temp variable would be a better idea in both cases IMHO.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^2: I use postfix dereferencing ...
by Eily (Monsignor) on Feb 06, 2019 at 15:38 UTC

You could even just write @$aref in your example.

Post deref can be more useful with more complex expressions like: $myobj->onemethod()->{blue}->anothermethod()->[4]->@* where you can read the thing in the order in which they happen (call onemethod, get the value at "blue", call anothermethod, get the value at 4, then deref), rather than @{ $myobj->onemethod()->{blue}->anothermethod()->[4] } where you read the steps from left to right, and the last one back on the left. I'd use a temp variable in both cases though.

Postderef can also help with slices where $some->{nested}{$complex{struct}}->@{qw<where I want more than one value>} is easier to read than @{$some->{nested}{$complex{struct}}}{qw<where I want more than one value>}. Again a temp variable would be a better idea in both cases IMHO.

[reply]
[d/l]
[select]

In Section Past Polls