So, clearly, we need to drop the % (modulo) operator since we all know that % is supposed to be a sigil, and we mustn't blur the lines between sigils and operators. Same goes for & and *, by the way. ** looks like a glob named '*' so certainly must not be used as an operator. %= looks like a special hash.

Actually, %= is a global hash. It is also the modulo-assignment operator.

 > say '%= = 0..9; $k = %=; $k %= %=;'
Argument "4/8" isn't numeric in modulus (%)
Argument "4/8" isn't numeric in modulus (%)
0
[download]

I find ->@* much less worrying than the above as the required prefix (->) is so much more explicit and visible. I'm not sure how I'd feel about the -> being optional in some cases (maybe it already is?).

Excellent example. Any variable =~ /^\Q$@%\E\W/ is, by convention, a special variable, and those that happen to be plain vanilla scalars, arrays or hashes currently, are special variable candidates as long as I know Perl books; and those should not be used as variables because:

• no guarantee exists that those will not have a special meaning in a future release of perl
• they look special and may be confused with operators and are confusing as part of their specialness

So - no, we need not drop the modulo operator - me must not use "%=" as a hash! And this

$\ = "\n";
*{'@*'} = sub { @{$_[0]} };
bless my $ref = [ qw(foo bar baz) ];

$method = '@*';

print for $ref->$method;
__END__
foo
bar
baz
[download]

while it works without use feature 'postderef', is plain weird - implementing the content of $method as a literal not less so.

And the mentioned part of demerphq's argument that you linked to:

    my @things= $foo->@*;

    So, now, the $ no longer can be relied to refer to a "scalar", it 
+might be a scalar, it might not.
[download]

Complains about a guarantee that already isn't assured:

my @things = $scalar->fetch_all_the_things();
[download]

so I find that argument quite unconvincing.

Come on, $scalar->fetch_all_the_things(); is a method call, and objects are just references held in scalars, just like scalar, hash and array references. But your example brings up my next objection: $ref->@* looks like $ref being an object. Is it? should it be? In my humble opinion: no. There's already enough overhead in each perl run.
Are we going in that direction, making everything into objects?

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.