Re: Problem with generics and dynamic array copy

From:

lewbloch <lewbloch@gmail.com>

Newsgroups:

comp.lang.java.programmer

Date:

Fri, 22 Jul 2011 13:33:35 -0700 (PDT)

Message-ID:

<f614944f-3a6c-41d6-9897-53f4da03cfa3@v11g2000prn.googlegroups.com>

On Jul 22, 12:27 pm, Robert Klemme <shortcut...@googlemail.com> wrote:

On 22.07.2011 20:36, Sebastian wrote:

Am 22.07.2011 20:23, schrieb markspace:

On 7/22/2011 10:30 AM, Sebastian wrote:

public static final <T> T[] arraycopy( T[] src )
{
Class<T> componentType = src.getClass().getComponentType(); // !!!=

RTFM. getComponentType() returns Class<?>, not Class<T>.

<http://download.oracle.com/javase/6/docs/api/java/lang/Class.html#get=

....>

public Class<?> getComponentType()

Returns the Class representing the component type of an array. If this
class does not represent an array class this method returns null.

well, yes, but given that src.getClass() must give one the class object
for arrays with component type T, why is the compiler not smart enough
to infer that the unknown class parameter in the return value of
getComponentType() must be T? As a human I can see that, that's why I
can cast to Class<T>, but I don't believe that I'm smarter than javac..=

The compiler has no idea what the semantics of getComponentType() is.
It could be implemented as

public Class<?> getComponentType() { return Object.class; }

and still be conformant to the declaration. Hence it cannot do any
automatic inference based on the fact you know that the array is T[].
Btw, you can actually pass B[] where B is a subclass of T.

Since Array.newInstance() accepts Class<?> you should simply use that -
that cast to T[] is needed anyway.

Of course, even better you scrap your implementation and use

http://download.oracle.com/javase/6/docs/api/java/util/Arrays.html#co...[=

],%20int%29

I'd say _best_ yet. In general, unless it really, really doesn't do
what you need, stick to the standard API instead of reinventing it.

This does, of course, require that you be aware of the API, but things
like 'java.util.Arrays' had better be part of your standard vocabulary
in any event.

Otherwise you have some upgrading to do on your skills.

--
Lew