NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
--Larry Wall in eval.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Brick (Score:2)
It's about a lot more than input validation. User input is only part of the problem, which is why Brick isn't built around it. The rules can be about anything and isn't tied to input fields or anything else. You figure out what constrains the system and build the rule set from that. You then use Brick to see if the current situation obeys the rules, and Brick tells you where it doesn't.
The use cases you describe (computing taxes, etc) aren't rules at all, but tasks. Rules constrain and define the systems actions. You'd use Brick to find out it your program is following the rules, although you have to decide on your own what to do when your program doesn't follow the rules.
Reply to This
Re: (Score:1)