8 messages in net.java.dev.rococoa.usersRe: nil| From | Sent On | Attachments |
|---|---|---|
| Duncan McGregor | Jul 17, 2009 8:01 am | |
| David Kocher | Jul 17, 2009 8:40 am | |
| Duncan McGregor | Jul 17, 2009 9:14 am | |
| David Kocher | Jul 17, 2009 3:52 pm | |
| Harald Kuhr | Jul 18, 2009 3:40 am | |
| Andrew Thompson | Jul 18, 2009 4:54 am | |
| Andrew Thompson | Aug 7, 2009 8:21 pm | |
| Duncan McGregor | Aug 10, 2009 8:00 am |
| Subject: | Re: nil | |
|---|---|---|
| From: | Harald Kuhr (hara...@gmail.com) | |
| Date: | Jul 18, 2009 3:40:02 am | |
| List: | net.java.dev.rococoa.users | |
On 17. juli. 2009, at 17.40, David Kocher wrote:
On 17.07.2009, at 17:01, Duncan McGregor wrote:
I'm trying to decide what I think, but here is a taster of the issues - if you call a ObjC method that is defined to return an NSObject, and the returned value is actually nil, should that return a Java null, or an instance of our Java NSObject that has nil inside it?
It should definitly return null. It makes programming against the API a lot more intuitive than to check for isNil() on the NSObject.
I'm also for returning null. The current implemententation has bitten me a couple of times, and I find it quite confusing.
Just wanted to let you know. I'm late, and it seems you are already on the right route. :-)
-- Harald K