Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

NS_ASSERT and Default Settings in Xcode

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

NS_ASSERT and Default Settings in Xcode

Subject: NS_ASSERT and Default Settings in Xcode
From: Andreas Grosam <email@hidden>
Date: Wed, 26 Aug 2009 10:47:51 +0200

When building a Cocoa project, I figured NS_ASSERT and friends macros are expanded to their respective code in the Release build in Xcode. This assumes that default settings have been directly inherited from a project template.

All other build environments that I know do disable (by default) assertion macros - and possibly define (or not define) macros which in effect strip the assertion code.

For Cocoa projects, the macro symbol NS_BLOCK_ASSERTIONS is responsible for controlling whether an NS_ASSERT is enabled or disabled.

Shouldn't it - by default - be defined in release builds in order to disable NS_ASSERT and friends?


Regards
Andreas Grosam
_______________________________________________
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


Follow-Ups:

Re: NS_ASSERT and Default Settings in Xcode
From: Jens Alfke <email@hidden>


Prev by Date:
Re: GCC 4.2 parse error in stl_algobase.h: "current namespace	'std'	does not enclose..."

Next by Date:
Re: Adding existing svn files to new project

Previous by thread:
Re: GCC 4.2 parse error in stl_algobase.h: "current namespace	'std'	does not enclose..."

Next by thread:
Re: NS_ASSERT and Default Settings in Xcode

Index(es):

Date
Thread