commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Benson <gudnabr...@yahoo.com>
Subject Re: [LANG] 3.0 StrTokenizer API change for next()
Date Sun, 15 Mar 2009 16:46:27 GMT



--- On Sun, 3/15/09, sebb <sebbaz@gmail.com> wrote:

> From: sebb <sebbaz@gmail.com>
> Subject: [LANG] 3.0 StrTokenizer API change for next()
> To: "Commons Developers List" <dev@commons.apache.org>
> Date: Sunday, March 15, 2009, 11:31 AM
> StrTokenizer implements ListIterator
> currently.
> 
> Given that it only deals in Strings, it could implement
> ListIterator<String>, however that would mean
> changing
> 
> public Object next()
> 
> to
> 
> public String next()
> 
> Any objections to implementing the above?
> 

1. A String _is_ an Object; I am convinced that narrowed return types are the right thing
to do in Java5-compatible code.  What reason could there be against it?
2. We have no obligation to be BC anyway.

-Matt

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


      

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


Mime
View raw message