|Welcome to the Monastery|
Case Exhaustion Treeby Xiong (Hermit)
|on Feb 02, 2014 at 20:33 UTC||Need Help??|
For some time now I've been obsessed with clean decision trees. No solution is appropriate for all needs and, as usual, tradeoffs are in play. Today I hacked out one particular way of simplifying these trees.
Here's the original mess, which usually worked but sometimes did not, and looks messy: fragile, unmaintainable. A block of code is set up for string eval:
Both $code or $args may be supplied or not; and an attempt is made to exhaust all four possible cases. As you can see, I've painted myself into such a corner that I've introduced a third input variable.
Another approach, which truly annoys me, is to nest conditionals:
This is so ugly and miserable I've rarely employed it. The second evaluation of the nested comparison, whatever it may be, is particularly offensive.
Alternatively, exhaust all four cases explicitly, at the cost of introducing two scratch flags:
Of course tim toady; and I don't doubt others will rush to display their favorite decision trees. This one may work for me sometimes.
Death only closes a Man's Reputation, and determines it as good or bad. —Joseph Addison