Mark, Right, again, my argument was less "IF-THENs rule and CASE-SWITCHes suck" than IF-THENs are easier to read/learn/are more transparent for non/novice-programmers.
Judy On Sun, 19 Feb 2006, Mark Wieder wrote: > Judy- > > Your example isn't a reasonable candidate for a switch/case construct > because the conditionals aren't at the same level. Instead your ifs > are nested within each other, and that's an example of where and > if/then/else construct is much more readable. There's no reason to > convert that. _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
