Re: Can this callback mechanism be generified?

Mark Space wrote:
> 
> Does this work? I didn't try it.  I think the "doCallback()" method is 
> ok without parameterized types... same with putting an unparameterized 
> type into the map.


My problem is that of associating the type (Date.class, line 23) with 
the type of my callback (line 15 and 24). There doesn't seem to be a way 
of expressing this. I would be ok with the erasure (implicit casting) 
issue, if only I got type safety and the developer got shielded from 
having to do the casting.

However, generifying the callback into:

     interface Callback<T>
     {
         String format(T object);
     }

....and trying to use that inside installCallback:

     public <T> void installCallback(Callback<T> callback)
     {
 
callbacks.put(callback.getClass().getTypeParameters()[0].getClass(), 
callback);
     }

....all I can get out is "T". Since this is by reflection, it is probably 
an erasure issue but it could also be because I'm not smart enough.

/Casper