This would seem to be a good chance to use exceptions.

Stylistically, I'd probably use sub refs instead of the string eval, too. If your pre- and post- conditions are in a package, UNIVERSAL::can comes to the rescue. Otherwise, this is an opportunity for a little symbol table muckery:

sub validate { my $input = shift; my %arg = @_; for (@{$arg{as}}) { my $func = "validate_$_"; my $package = __PACKAGE__ . '::'; no strict 'refs'; if (exists ${ $package }{$func}) { $func = *{ ${ $package }{$func} }{CODE}; return unless $func->($input); } else { # throw exception and/or return } } warn "validated $input"; return 1; }
Or you could build a hashref of validators, or cache them instead of explicitly going to the symbol table, or use the Listener pattern, or do all sorts of things.

In reply to Re: An example of programming by contract by chromatic
in thread An example of programming by contract by princepawn

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.