Currently, as it stands, this system will trigger a warning if the $input isn't a number of some sort. That's because of the >= in the non_negative validation.

Also, what if I did something like

validate($input, as => ['blah']);
Since $validate{'blah'} doesn't exist, you end up with a fatal error. A simple (if uninformative) change would be to
for (@{$args{as}}) { my $func = $validate{$_} || next; my $r = $func->($input); die "$_ validation failed" unless $r; }
Better would be to throw some exception or warning.

Furthermore, you do know that this will be less efficient, execution-wise, than just putting the checks into the program. This methdology is best if you plan on doing the same checks on a large variety of inputs. (Of course, you're just playing, which is cool.)

One possibility is to, instead of forcing the user to validate the input, have the function validate its own input using these functions. Or, maybe a wrapper around factorial(). That way, everything is encapsulated.

------
We are the carpenters and bricklayers of the Information Age.

Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement.


In reply to Re: Programming by Contract Example. revised by dragonchild
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.