Re: argument checks
Re: argument checks
- Subject: Re: argument checks
- From: Michael Watson <email@hidden>
- Date: Thu, 12 Jun 2008 22:06:50 -0400
You can use #import in straight C applications from within Xcode, if
you like. There's also nothing stopping you from using the #include
directive in Objective-C. It's just more work than #import, which
handles include cycles for you.
--
m-s
On 12 Jun, 2008, at 21:37, William Squires wrote:
I thought ObjC used "#import", not "#include", so that multiple
copies of a header wouldn't appear, but maybe that's just for Cocoa
stuff, and not for "ordinary" C?
On Jun 12, 2008, at 1:05 AM, Jason Coco wrote:
#include <assert.h>
/* ... */
NSNumber *myNum = nil;
// Lots of code where you've forgotten to actually do anything with
myNum
assert( myNum != nil );
results = [myClass someCalculationUsing: myNum];
// lots more code
to remove the assertion in the release build, compile with -DNDEBUG
HTH, /jason
On Jun 12, 2008, at 01:50 , Ashley Perrien wrote:
Noob question: I'm putting together a small code library and I'm
trying to include some error checking in the methods; what I want
to protect against is the following:
NSNumber *myNum;
// Lots of code where I've forgotten to actually do anything with
myNum
results = [myClass someCalculationUsing: myNum];
myNum in this case is an object and does exist but it's not a
valid, usable argument. So in the implementation I'd like to have
something along the lines of:
if (myNum == nil)
NSLog(@"some error message");
but can't figure out what to check for that would get me into the
error message condition. Any suggestions?
Ashley Perrien
_______________________________________________
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden