Decision-ParseTree
view release on metacpan - search on metacpan
view release on metacpan or search on metacpan
lib/Decision/ParseTree.pm view on Meta::CPAN
=item * the key is the method to run in the rules object
=item * the value must be an arrayref or hashref
=back
=item * ARRAYS are a series of rules run in order
=item * HASHES are a series of answers
=item * SCALARS are endpoints
=back
=head2 Why add more parts, why blow everything in to separate objects.
Sometimes you have to make things messy before they can get clean.
Theres a flexibility that comes with breaking things apart in to nice, neat
little chunks. By separating the rule logic in to one place you can make
very complex rules that do not gunk up your code. You pull the order of these
view all matches for this distributionview release on metacpan - search on metacpan
( run in 1.228 second using v1.00-cache-2.02-grep-82fe00e-cpan-4673cadbf75 )