Using @Argument.Check for things other than mere checking

[bill.ma...@gmail.com]

Is it a bad idea to use the method annotated with @Argument.Check for
things which go beyond mere checking? Say, initializing other
instance variables whose values depend on the annotated Arguments?

[dramage]

That seems like a perfectly reasonable thing to do. The only
semantics garunteed for @Argument.Check methods will be called exactly
once after the class has been instantiated and argument fields have
been filled in; and that exceptions thrown within the method will be
caught and displayed as part of the usage string. I don't see these
semantics as incompatible with other sorts of initialization.

dan