Re: Analyzer warning about garbage with double return values
Re: Analyzer warning about garbage with double return values
- Subject: Re: Analyzer warning about garbage with double return values
- From: Jean-Daniel Dupas <email@hidden>
- Date: Wed, 2 Sep 2009 11:15:23 +0200
Le 2 sept. 2009 à 11:07, Markus Spoettl a écrit :
On Sep 2, 2009, at 10:58 AM, Bjoern Knafla wrote:
Its hidden in the following info box text from the link http://developer.apple.com/mac/library/documentation/Cocoa/Conceptual/ObjectiveC/Articles/ocObjectsClasses.html#//apple_ref/doc/uid/TP30001163-CH11-SW7
:
Note: The behavior of sending messages to nil changed slightly with
Mac OS X v10.5.
On Mac OS X v10.4 and earlier, a message to nil also is valid, as
long as the message returns an object, any pointer type, void, or
any integer scalar of size less than or equal to sizeof(void*); if
it does, a message sent to nil returns nil. If the message sent to
nil returns anything other than the aforementioned value types (for
example, if it returns any struct type, any floating-point type, or
any vector type) the return value is undefined. You should
therefore not rely on the return value of messages sent tonil
unless the method’s return type is an object, any pointer type, or
any integer scalar of size less than or equal to sizeof(void*).
Which appears to be describing behavior in 10.4 and earlier -
otherwise it would directly contradict the bullet points above the
box.
As mentioned I'm compiling against the 10.5 Base SDK.
The target OS is not defined by the SDK but by the "Deployment Target"
build setting.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden