Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

After lunch, before Christmas 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • In 30 minutes, I didn't really have time to get into depth with Brick. Oh well.

    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,
    • What I like about it is that it seems to provide a bridge between business types and coding types with its clear language. I think that is a really, really important advancement that has been ignored. It is a pity since with more understanding from those who pay for programming, more and better programming could be done, IMHO.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.