Re: NSSelector<T> - a curiosity
Re: NSSelector<T> - a curiosity
- Subject: Re: NSSelector<T> - a curiosity
- From: Mike Schrag <email@hidden>
- Date: Thu, 8 May 2008 10:21:35 -0400
Don't know about the "looking up" part... AFAIK return types are not
a part of the method signature in Java, also indicated by Class API,
whose "getMethod..." stuff does not ask for the return type as a
parameter...
Well, it's technically part of the method signature, but it is not
required for lookup (because java only supports covariant return types
so there's never a conflict for a lookup). Curiously, getReturnType()
on a void method returns "void" -- some magical class -- like how you
can refer to "int.class" in code and it works even though there is no
class of that type. It's possible that internally "void" maps to
Void.class, but if it does, it's totally magical. Also, void is not
assignable from Void and vice versa, so internally the VM believes
they are different types. So basically the mystery continues as to
what the point of Void.class is :)
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden