commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Pitts (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LANG-296) Add method chaining pattern to StopWatch
Date Thu, 09 Nov 2006 03:21:39 GMT
    [ http://issues.apache.org/jira/browse/LANG-296?page=comments#action_12448356 ] 
            
Justin Pitts commented on LANG-296:
-----------------------------------

Well, in the case of this class, I would guess that typical usage patterns
are:
create -> start
stop->read
split -> read

It makes sense to me, this is how I find my team using the class.

However, if one of the underlying constraints of the framework is to
preserve binary compatability, then it makes no difference. My frustration
is that constraint ought to be made clear on the page describing
contributions.



> Add method chaining pattern to StopWatch
> ----------------------------------------
>
>                 Key: LANG-296
>                 URL: http://issues.apache.org/jira/browse/LANG-296
>             Project: Commons Lang
>          Issue Type: Improvement
>    Affects Versions: 2.2
>         Environment: any
>            Reporter: Justin Pitts
>            Priority: Trivial
>         Attachments: MethodChainingPattern
>
>
> Implement the method chaining pattern (similiar to StringBuffer) to mutator methods.
This enables the following code:
> StopWatch s = new StopWatch().start();
> System.out.println(s.stop().getTime());

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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