On Jul 16, 2009, at 15:54, Quincey Morris wrote:
On Jul 16, 2009, at 15:19, Timothy Wood wrote:
then at "xxx" you'd like to build a new NSError that has *outError
(if outError != NULL) as the underlying error....
It seems to be you have this precisely upside-down. outError is an
output parameter, not an an input-output parameter. There *is* no
input value of *outError that can become the underlying error.
Well, I did misunderstand, by not reading carefully enough. But I'd
still be interested to see an example of the code with the macro in
place. Is 'outError' a parameter to the macro at xxx? If so, why
wouldn't you just pass nil as the parameter at yyy?
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please 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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
