Yeah, presuming an OOP context lots of branches may indicate you should use the "Replace Conditional with Polymorphism" refactoring. Push the different conditional behaviors down into a method in child classes and just call that method.
But again, that presumes a set of circumstances which may not apply in this case.
| [reply] |
Yeah, presuming an OOP context lots of branches may indicate you should use the "Replace Conditional with Polymorphism" refactoring.
Indeed, but not only limited to this case. Of course newbies coming from other languages happen to abuse them where e.g. a hash would have been enough, not to say the best thing! But then again it's not something one can know in advance, from a generic point of view. I only did that remark in the hope that it may have been useful to the OP or to anyone else who will subsequently read the thread.
| [reply] |
Optionally, the nested ternary is good for long chains of if/elsif/else
#! /usr/bin/perl -w
use strict;
(my $foo = shift) ||= 0;
($foo == 1) ? print "It's one\n" :
($foo == 2) ? print "It's two\n" :
($foo == 3) ? print "It's three\n" :
print "It's nothing meaningful!\n";
| [reply]
[d/l] |
Personally I try to avoid using?: for its side effects, when not golfing - that is! Re the example you gave, a hash or an array would have provided a much neater solution.
| [reply]
[d/l] |