[ http://issues.apache.org/jira/browse/LANG-296?page=comments#action_12448186 ] Henri Yandell commented on LANG-296: ------------------------------------
My general usage has been to use chaining when things are similar, so: foo.setOne(...).setTwo(...).setThree(....) Having a getFour() on the end seems confusing, so in this case I would just use: s.stop().start().split() etc. There seems no value to that, so all we're really allowing here is chaining of mutator->accessor and not mutator->mutator->mutator. That doesn't seem that useful. Anyone have any thoughts? > 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
