Originally posted by Dale Smirth:
... Are there any pros or cons to either using a constructor or method? ...
Consider that a constructor's job is basically getting an instance of that class ready for use (constructing an object). It really depends on what you have in mind for this class, but if the purpose is just to "evaluate" variables, then it seems that a method might be more appropriate, so that you're not creating a new object every time you want to evaluate a new set of varibles. In fact, a
static method might be best, because then you wouldn't even need an instance. (As Jean-Sebastien Abella pointed out above, see "factory method.")