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] New: - Why are the methods of TTest not static?
Date Mon, 13 Dec 2004 13:56:09 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

           Summary: Why are the methods of TTest not static?
           Product: Commons
           Version: 1.0 Final
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Math
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: M.E.Foster@ed.ac.uk


To do T-tests on data -- for which many thanks! -- you currently have to do the
following

TTest tester = new TTestImpl();
tester.pairedTTest( ... );

There are two things that are inelegant about this implementation: you have to
explicitly call "new TTestImpl()" instead of using a factory method, and I don't
see why there's this whole interface-implementation paradigm at all. As far as I
can see, there's no state stored in the TTest implementation; why isn't it a
singleton class with static methods instead?

-- 
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