commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 32663] - [math] Why are the methods of TTest not static?
Date Mon, 13 Dec 2004 21:54:29 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32663>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32663





------- Additional Comments From phil@steitz.com  2004-12-13 22:54 -------
Great questions.  The interface / implementation separation is to support the 
strategy pattern for alternative implementations.  Staying away from static 
methods in implementations is for extensibility.  All that said, I agree that 
the setup is a little awkward.  

One way to improve usability would be to introduce a TestUtils class that 
would work similarly to StatUtils -- create singleton instances of the 
implementation classes and expose static methods that delegate to the 
singletons.  Any better ideas?  Patches welcome.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message