All the Perl that's Practical to Extract and Report
use Perl Log In
kaare (663)
(email not shown publicly)
After lunch, before Christmas
Like everybody else, I'm anxious about the frontline development in Perl. So I attended
- Leon Brocard (acme) - What's new in Perl 5.10?
- brian d foy - Learning Perl 6
- Jonathan Worthington - Classes, Roles and Constraints in Perl 6
- Nelson Ferraz - Adventures in Perl6
All very, very nice presentations. Just like the first time I read the Apocalypses, I will say: "Gimme now!"
Can't wait for Christmas...
I also attended
- brian d foy - Flexible Business Rules with Brick
I still can't really figure out which problem domain Brick is solving. Brian talked about Business Rules, but in reality described a Next Generation Input Validator. For me Business Rules are all about computing taxes, deciding how to do the accounting for your automatic invoicing etc. Perhaps the validator is only first step?
If I weren't so tired Sunday afternoon, I would have bugged Brian, but at that time I could think of nothing more than my nice, soft couch.
I guess I'll try to catch Brian another time, perhaps there is a mailing list or an IRC channel.
There were a lot of other very fine talks, and the event went really, really smooth. Hard to top next time!
Fooled me :-) Maybe the Perlian sentence modifier style has crept into
your C...? I know that I often stare at the C compiler moaning about
my perfectly sensible 'print "$p\n";'...
-- Jarkko Hietaniemi
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,
Re: (Score:1)