Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
... I'm not sure why defined/undef &{'walk'} are allowed.

I'm sure others can cite a precise historical development of the usage of strictures, but for me it's a question of expedience.

The use of symbolic references is not discouraged because symbolic references are Evil, but because in certain cases experience has shown them to cause much trouble. These particular cases are foreclosed by  use strict 'refs';

Some cases are both useful and entirely safe. Testing for the definition of a subroutine with
    defined &{ 'subroutine_name' }
is obviously so.

An indispensable use is the very creation of a hard reference in the first place. It's hard to see how some statement like
    my $coderef = \&{ 'subroutine_name' };
is not going to be involved. Indeed, all the following work (and why should they not?)
    my $coderef = \&subroutine_name;
    my $coderef = \&{subroutine_name};
    my $coderef = \&{ 'subroutine_name' };
although  &{subroutine_name} produces an "Ambiguous use of..." warning.

The final case you mention is the potentially very useful  undef &{ 'subroutine_name' };   One can imagine doing this via a hard reference, e.g.
    my $coderef = \&{ 'subroutine_name' };
    undef $$coderef;
or some such roundabout implementation (that one doesn't actually work, BTW), but what would be the point? After all, it's the name of the subroutine that ultimately has to be undefined; just going to the address of the actual code and scribbling something over it (a return? a jump to an exception?) would not seem to gain you very much.

Anyway, my USD0.02.

In reply to Re: undef/defined &{$name} while "strict refs" by AnomalousMonk
in thread undef/defined &{$name} while "strict refs" by anazawa

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others cooling their heels in the Monastery: (2)
    As of 2018-04-24 00:09 GMT
    Find Nodes?
      Voting Booth?