Re: NSSelector<T> - a curiosity
Re: NSSelector<T> - a curiosity
- Subject: Re: NSSelector<T> - a curiosity
- From: Michael Scott <email@hidden>
- Date: Wed, 07 May 2008 15:35:20 +0800
- Thread-topic: NSSelector<T> - a curiosity
NSSelector<Object> works fine. But it is a bit wonky.
Perhaps Java should allow 'null' as a type argument.
Probably a bit much to ask just to make an old NextStep class more
consistent.
On 7/5/08 2:11 PM, "Anjo Krank" <email@hidden> wrote:
> Try to cheat an use <Object>?
>
> Am 07.05.2008 um 04:12 schrieb Michael Scott:
>
>> NSSelector has been generified (generifried?) so that the return
>> type of the method it calls must be specified as a type parameter.
>>
>> So,
>> NSSelector<String> selector = new
>> NSSelector<String>(³testMethod²);
>>
>> Can be used to call the following method which returns a String
>> (regardless on what class the method resides):
>>
>> public String testMethod() {
>> return ³testing, testing, 1, 2, 3 ...²;
>> }
>>
>> But what if the method returns void?
>>
>> public void testMethod2() {
>> // do something fab
>> }
>>
>> What type argument should be used to instantiate NSSelector<T>?
>>
>> Or have I missed something fundamental?
>>
>> Cheers
>> Michael Scott
>>
>>
>>
>> _______________________________________________
>> 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
>
_______________________________________________
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