use constant PUBLIC => 0, PRIVATE => 1; %query = ( action1 => { visibility => PUBLIC, code => \&handler1, }, action2 => { visibility => PUBLIC, code => \&handler2, }, action3 => { visibility => PRIVATE, code => \&_do_not_advertise, }, ); my @public_actions = grep $query{$_}->{visibility} == PUBLIC, keys %query;

If that's too verbose, just make subs which do the same thing (e.g. register_private( action3 => \&_do_not_advertise )). Or encapsulate things in a class and make visibility a method.

Update: Or just have a register sub which takes an action name and a sub name and then adds the right elements.

sub register_action { my( $action, $subname ) = @_; no strict 'refs'; $query{ $action } = { visibility => ($subname =~ /^_/), code => \&{$subname} }; }

In reply to Re: Getting name of sub from a hash-based dispatch table? by Fletch
in thread Getting name of sub from a hash-based dispatch table? by theguvnor

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.