commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: [pool] CursorableLinkedList - why does it use a mix of <T>, Object and <E> ?
Date Wed, 13 Oct 2010 00:54:59 GMT
On 13 October 2010 01:15, Paul Benedict <pbenedict@apache.org> wrote:
> The whole <E> convention comes from java.util where there are
> "elements" of a collection.

Yes, I know.

> I don't like to mix things. I think type T
> would be find everywhere unless you have multiple types and need a
> memorable letter.

As far as I can tell, the collection only supports a single type,
similar to List<E>, and one would not expect to see other types used
in such a List class.

But I could be wrong which is why I was asking.

Since j.u.List uses <E>, I think it would make sense use <E> here as well.

> On Tue, Oct 12, 2010 at 6:21 PM, sebb <sebbaz@gmail.com> wrote:
>> 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
>
>

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


Mime
View raw message