I'm also going with ~>. Visually the squiggle (tilde), to me, looks like a "tentative dereference".
Btw, I really can't wait. I'll be able to pull horrible hacky code such as:
package MyApp::Universal;
use warnings; use strict;
use Try::Tiny;
sub deref {
#
# Weak linear dereferencing. $foo->deref('bar','baz')
# is almost like $foo->bar->baz except we'll
# return undef rather than barfing if 'foo'
# or 'bar' evaulate to undef.
#
if (@_ >= 2) {
my $ref = shift;
my $deref = shift;
return unless defined $ref
&& defined $deref
&& try {$ref->can('isa')};
return deref($ref->$deref => @_);
}
elsif (@_) {
return shift;
}
else {
return;
}
}
They I can go through my code and refactor....
$obj->deref(qw(foo bar baz));
as....
$obj~>foo~>bar~>baz;
Update Also look forward to be able to do...
$href~>{foo}~>[$bar]~>{baz};
...when I don't want autovivification.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|