Re^8: use feature 'postderef'; # Postfix Dereference Syntax is coming in 5.20 (demerphq mistaken?)

That's not how context works at all

I'm baffled. So you are telling me that I don't know about context in Perl?

%{ ... } evaluates to a hash or a list.

And how, pray, is the "or" resolved? There.

Anyways, you are right. Im sick of tennis match like conversations. I'm not here to win.

perl -le'print map{pack c,($-++?1:13)+ord}split//,ESEL'

Comment on Re^8: use feature 'postderef'; # Postfix Dereference Syntax is coming in 5.20 (demerphq mistaken?)

Replies are listed 'Best First'.
Re^9: use feature 'postderef'; # Postfix Dereference Syntax is coming in 5.20 (demerphq mistaken?) by ikegami (Patriarch) on Dec 03, 2013 at 02:28 UTC
I'm baffled. So you are telling me that I don't know about context in Perl? I can't comment on what you know, just on what you say. Context doesn't cause values to be coerced. Operators return different values based on the context. That's why `$x = (4,5,6);` and `@a = (4,5,6); $x = @a;` result in different values in `$x`. And how, pray, is the "or" resolved? There. I'm not sure what the means. Are you asking how it's determined when `%...` evaluates to a hash and when `%...` evaluates to a list? It's based on the operator that parses it. e.g. `keys(%foo)` or `\%foo` vs `print(%foo)`.	[reply] [d/l] [select]
Re^9: use feature 'postderef'; # Postfix Dereference Syntax is coming in 5.20 (demerphq mistaken?) by Anonymous Monk on Dec 01, 2013 at 21:14 UTC
Anyways, you are right. Im sick of tennis match like conversations. I'm not here to win. you'll never be pope with that attitude ;) :D	[reply]