Re: Is this a bug of the Cocoa or the Objective-C?
Re: Is this a bug of the Cocoa or the Objective-C?
- Subject: Re: Is this a bug of the Cocoa or the Objective-C?
- From: JongAm Park <email@hidden>
- Date: Fri, 26 Jan 2007 11:18:35 -0800
Hmm..
Yeah.. it was documented.
However, one thing is not explained.
When it returns nil or 0, it doesn't update the NSRange variable.
I understand that a scalar value can't be assigned to a vector structure.
However, it should be explained somewhere that the content of the vector
structure is not changed
when the nil value is tried to be assigned to the structure.
Thank you for the link, though.
Joar Wingfors wrote:
On Jan 26, 2007, at 5:07 PM, JongAm Park wrote:
However, it was not documented, or somewhere it was documented but I
didn't read it
or I forgot it.
It's documented in a lot of places, here are two examples:
<http://developer.apple.com/documentation/MacOSX/Conceptual/universal_binary/universal_binary_tips/chapter_5_section_22.html>
<http://developer.apple.com/documentation/Cocoa/Conceptual/ObjectiveC/Articles/chapter_4_section_3.html>
It would be good if the Objective-C runtime can check if the scalar
value, i.e nil, is
tried to be assigned to the NSRange, ie. a vector structure, and can
raise some exception.
File enhancement requests.
j o a r
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden