package Base;

sub AUTOLOAD {
    (my $meth = our $AUTOLOAD) =~ s/([^:]+)$/$1/;

    if ( $meth =~ /^is_/ ) {
        return;
    }

    # ????
}

package Foo;

our @ISA = qw( Base );

sub is_foo { 1 }

package Bar;

our @ISA = qw( Base );

sub is_bar { 1 }

# And so forth

[download]
I anticipate having dozens of these sibling classes, so I don't want Base to have to have a sub is_(whatever) { 0 }. Each one only declares the sub is_(whatever) { 1 } that it is. I don't want to use isa() cause the classnames are much longer and it's just ugly. And, frankly, this should be do-able. But, I don't want AUTOLOAD to catch methods that aren't of the form /^is_/. I want it to fail as if it wasn't there.
My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

In reply to Redispatching AUTOLOAD for failure by dragonchild

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.