Sorry but your ideas are not trivial or easy to grasp, so I have to go little by little. =)

I find the desired short cut behaviour to catch undef even more problematic than the rest.

I'd rather prefer a catch_undef { BLOCK } command, because the block would be explicit about what is caught without much explanation.

This can be emulated (at least) with

my $h_b = {};
my $x   = eval {
    use warnings FATAL => 'uninitialized' ;
    $h_b->{velocity}." mph";
} // 'unknown';

print $x;

[download]

I tried to construct some syntactic sugar

sub catch_undef (&) {
    my $code_ref = shift;
    
    eval {
        use warnings FATAL => 'uninitialized' ;
        $code_ref->()
    };
}

[download]

but I'm running into two problems:

1) Obviously pragmas are lexically scoped, I seem to remember there are some obscure tricks to manipulate the warning flags of a coderef (something with $^H ?) but I'm too lazy at the moment.

2) seems to be a bug in the parser, because I get a weird syntax error for

 catch_undef { $ref->{velocity} .'mph' }  //  "unknown";

Too many arguments for main::catch_undef at /tmp/tst.pl line 29, near "//  "unknown""

using || instead solves the parsing problem (but not the task)

Cheers Rolf
(addicted to the Perl Programming Language and ☆☆☆☆ :)
Je suis Charlie!

In reply to Re^3: RFC: The lightning-rod operator by LanX
in thread RFC: The lightning-rod operator by martin

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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! —
  • 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:
    & &amp;
    < &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.