commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <GGreg...@seagullsoftware.com>
Subject RE: [pool] CursorableLinkedList - why does it use a mix of <T>, Object and <E> ?
Date Tue, 12 Oct 2010 23:27:38 GMT
While we are on the topic of CursorableLinkedList, I wonder if j.u.c provides a data structure
that we could use and avoid maintaining CursorableLinkedList?

Gary

> -----Original Message-----
> From: sebb [mailto:sebbaz@gmail.com]
> Sent: Tuesday, October 12, 2010 16:22
> To: Commons Developers List
> Subject: [pool] CursorableLinkedList - why does it use a mix of <T>, Object
> and <E> ?
> 
> CursorableLinkedList is based on the type T, and removeFirst() returns
> T, yet getFirst() returns Object.
> 
> Also, toArray() returns Object[] or E[].
> 
> Not sure I follow why there is this mixture?
> 
> ---------------------------------------------------------------------
> 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