Functions

Basic retain operation... calls [NSObject -retain]
Does nothing when ARC is in use.
Basic release operation... calls [NSObject -release]
Does nothing when ARC is in use.
Basic autorelease operation... calls [NSObject -autorelease]
Does nothing when ARC is in use.
Tested retain - only invoke the objective-c method if the receiver is not nil.
Does nothing when ARC is in use.
Tested release - only invoke the objective-c method if the receiver is not nil.
Does nothing when ARC is in use.
Tested autorelease - only invoke the objective-c method if the receiver is not nil.
Does nothing when ARC is in use.
ASSIGN(object,value) assigns the value to the object with appropriate retain and release operations.
Use this to avoid retain/release errors.
ASSIGNCOPY(object,value) assigns a copy of the value to the object with release of the original.
Use this to avoid retain/release errors.
ASSIGNMUTABLECOPY(object,value) assigns a mutable copy of the value to the object with release of the original.
Use this to avoid retain/release errors.
DESTROY() is a release operation which also sets the variable to be a nil pointer for tidiness - we can't accidentally use a DESTROYED object later. It also makes sure to set the variable to nil before releasing the object - to avoid side-effects of the release trying to reference the object being released through the variable.
DEALLOC calls the superclass implementation of dealloc, unless ARC is in use (in which case it does nothing).
ENTER_POOL creates an autorelease pool and places subsequent code in a block.
The block must be terminated with a corresponding LEAVE_POOL.
You should not break, continue, or return from such a block of code (to do so could leak an autorelease pool and give objects a longer lifetime than they ought to have. If you wish to leave the block of code early, you should ensure that doing so causes the autorelease pool outside the block to be released promptly (since that will implicitly release the pool created at the start of the block too).
LEAVE_POOL terminates a block of code started with ENTER_POOL.
Compile-in X if (and only if) ARC is not in use. This is provided to handle obscure cases not covered by the other macros.
DEPRECATED... use IF_NO_ARC() instead.
DEPRECATED... use ENTER_POOL and LEAVE_POOL and make sure your code does not break/continue/return out of the section of code.
DEPRECATED... use ENTER_POOL and LEAVE_POOL and make sure your code does not break/continue/return out of the section of code.

This function (macro) is a GNUstep extension.

_(@"My string to translate")

is basically equivalent to

NSLocalizedString(@"My string to translate", @"")

It is useful when you need to translate an application very quickly, as you just need to enclose all strings inside _(). But please note that when you use this macro, you are not taking advantage of comments for the translator, so consider using NSLocalizedString instead when you need a comment.

You may define GS_LOCALISATION_BUNDLE_ID to the bundle identifier of the bundle which is to provide the localisation information.
This can be used when compiling a single file by specifying something like '-D GS_LOCALISATION_BUNDLE_ID=$(FRAMEWORK_NAME)' in your make file.
If this is not defined, the localisation is provided by your application's main bundle exactly like the NSLocalizedString function.

Alternatively you may define GS_LOCALISATION_BUNDLE to be the bundle to be used to prvide the localisation information.

This function (macro) is a GNUstep extension.

__(@"My string to translate")

is exactly the same as

GSLocalizedStaticString(@"My string to translate", @"")

It is useful when you need to translate an application very quickly. You would use it as follows for static strings:

NSString *message = __(@"Hello there");... more code... NSLog (_(messages));

But please note that when you use this macro, you are not taking advantage of comments for the translator, so consider using GSLocalizedStaticString instead when you need a comment.

This function (macro) is a GNUstep extensions, and it is used to localize static strings. Here is an example of a static string:

NSString *message = @"Hi there";... some code... NSLog (message);

This string can not be localized using the standard openstep functions/macros. By using this gnustep extension, you can localize it as follows:

NSString *message = GSLocalizedStaticString (@"Hi there", @"Greeting");... some code... NSLog (NSLocalizedString (message, @""));

When the tools generate the Localizable.strings file from the source code, they will ignore the NSLocalizedString call while they will extract the string (and the comment) to localize from the GSLocalizedStaticString call.

When the code is compiled, instead, the GSLocalizedStaticString call is ignored (discarded, it is a macro which simply expands to key), while the NSLocalizedString will actually look up the string for translation in the Localizable.strings file.

Please note that there is currently no macro/function to localize static strings using different tables. If you need that functionality, you have either to prepare the localization tables by hand, or to rewrite your code in such a way as not to use static strings.

To be used inside a method for making sure that a range does not specify anything outside the size of an array/string. Raises exception if range extends beyond [0,size]. Size must be an unsigned integer (NSUInteger).
Checks whether INDEX is strictly less than OVER (within C array space). INDEX and OVER must be unsigned integers (NSUInteger).

CREATE_AUTORELEASE_POOL

Basic retain operation... calls [NSObject -retain]
Does nothing when ARC is in use.
Basic release operation... calls [NSObject -release]
Does nothing when ARC is in use.
Basic autorelease operation... calls [NSObject -autorelease]
Does nothing when ARC is in use.
Tested retain - only invoke the objective-c method if the receiver is not nil.
Does nothing when ARC is in use.
Tested release - only invoke the objective-c method if the receiver is not nil.
Does nothing when ARC is in use.
Tested autorelease - only invoke the objective-c method if the receiver is not nil.
Does nothing when ARC is in use.
ASSIGN(object,value) assigns the value to the object with appropriate retain and release operations.
Use this to avoid retain/release errors.
ASSIGNCOPY(object,value) assigns a copy of the value to the object with release of the original.
Use this to avoid retain/release errors.
ASSIGNMUTABLECOPY(object,value) assigns a mutable copy of the value to the object with release of the original.
Use this to avoid retain/release errors.
DESTROY() is a release operation which also sets the variable to be a nil pointer for tidiness - we can't accidentally use a DESTROYED object later. It also makes sure to set the variable to nil before releasing the object - to avoid side-effects of the release trying to reference the object being released through the variable.
DEALLOC calls the superclass implementation of dealloc, unless ARC is in use (in which case it does nothing).
ENTER_POOL creates an autorelease pool and places subsequent code in a block.
The block must be terminated with a corresponding LEAVE_POOL.
You should not break, continue, or return from such a block of code (to do so could leak an autorelease pool and give objects a longer lifetime than they ought to have. If you wish to leave the block of code early, you should ensure that doing so causes the autorelease pool outside the block to be released promptly (since that will implicitly release the pool created at the start of the block too).
LEAVE_POOL terminates a block of code started with ENTER_POOL.
Compile-in X if (and only if) ARC is not in use. This is provided to handle obscure cases not covered by the other macros.
DEPRECATED... use IF_NO_ARC() instead.
DEPRECATED... use ENTER_POOL and LEAVE_POOL and make sure your code does not break/continue/return out of the section of code.

DEALLOC

DESTROY

ENTER_POOL

GSLocalizedStaticString

This function (macro) is a GNUstep extension.

_(@"My string to translate")

is basically equivalent to

NSLocalizedString(@"My string to translate", @"")

Alternatively you may define GS_LOCALISATION_BUNDLE to be the bundle to be used to prvide the localisation information.

This function (macro) is a GNUstep extension.

__(@"My string to translate")

is exactly the same as

GSLocalizedStaticString(@"My string to translate", @"")

It is useful when you need to translate an application very quickly. You would use it as follows for static strings:

NSString *message = __(@"Hello there");... more code... NSLog (_(messages));

But please note that when you use this macro, you are not taking advantage of comments for the translator, so consider using GSLocalizedStaticString instead when you need a comment.

This function (macro) is a GNUstep extensions, and it is used to localize static strings. Here is an example of a static string:

NSString *message = @"Hi there";... some code... NSLog (message);

This string can not be localized using the standard openstep functions/macros. By using this gnustep extension, you can localize it as follows:

NSString *message = GSLocalizedStaticString (@"Hi there", @"Greeting");... some code... NSLog (NSLocalizedString (message, @""));

When the tools generate the Localizable.strings file from the source code, they will ignore the NSLocalizedString call while they will extract the string (and the comment) to localize from the GSLocalizedStaticString call.

GS_LOCALISATION_BUNDLE

This function (macro) is a GNUstep extension.

_(@"My string to translate")

is basically equivalent to

NSLocalizedString(@"My string to translate", @"")

Alternatively you may define GS_LOCALISATION_BUNDLE to be the bundle to be used to prvide the localisation information.

GS_RANGE_CHECK

This function (macro) is a GNUstep extension.

_(@"My string to translate")

is basically equivalent to

NSLocalizedString(@"My string to translate", @"")

Alternatively you may define GS_LOCALISATION_BUNDLE to be the bundle to be used to prvide the localisation information.

This function (macro) is a GNUstep extension.

__(@"My string to translate")

is exactly the same as

GSLocalizedStaticString(@"My string to translate", @"")

It is useful when you need to translate an application very quickly. You would use it as follows for static strings:

NSString *message = __(@"Hello there");... more code... NSLog (_(messages));

But please note that when you use this macro, you are not taking advantage of comments for the translator, so consider using GSLocalizedStaticString instead when you need a comment.

This function (macro) is a GNUstep extensions, and it is used to localize static strings. Here is an example of a static string:

NSString *message = @"Hi there";... some code... NSLog (message);

This string can not be localized using the standard openstep functions/macros. By using this gnustep extension, you can localize it as follows:

NSString *message = GSLocalizedStaticString (@"Hi there", @"Greeting");... some code... NSLog (NSLocalizedString (message, @""));

IF_NO_ARC

Basic retain operation... calls [NSObject -retain]
Does nothing when ARC is in use.
Basic release operation... calls [NSObject -release]
Does nothing when ARC is in use.
Basic autorelease operation... calls [NSObject -autorelease]
Does nothing when ARC is in use.
Tested retain - only invoke the objective-c method if the receiver is not nil.
Does nothing when ARC is in use.
Tested release - only invoke the objective-c method if the receiver is not nil.
Does nothing when ARC is in use.
Tested autorelease - only invoke the objective-c method if the receiver is not nil.
Does nothing when ARC is in use.
ASSIGN(object,value) assigns the value to the object with appropriate retain and release operations.
Use this to avoid retain/release errors.
ASSIGNCOPY(object,value) assigns a copy of the value to the object with release of the original.
Use this to avoid retain/release errors.
ASSIGNMUTABLECOPY(object,value) assigns a mutable copy of the value to the object with release of the original.
Use this to avoid retain/release errors.
DESTROY() is a release operation which also sets the variable to be a nil pointer for tidiness - we can't accidentally use a DESTROYED object later. It also makes sure to set the variable to nil before releasing the object - to avoid side-effects of the release trying to reference the object being released through the variable.
DEALLOC calls the superclass implementation of dealloc, unless ARC is in use (in which case it does nothing).
ENTER_POOL creates an autorelease pool and places subsequent code in a block.
The block must be terminated with a corresponding LEAVE_POOL.
You should not break, continue, or return from such a block of code (to do so could leak an autorelease pool and give objects a longer lifetime than they ought to have. If you wish to leave the block of code early, you should ensure that doing so causes the autorelease pool outside the block to be released promptly (since that will implicitly release the pool created at the start of the block too).
LEAVE_POOL terminates a block of code started with ENTER_POOL.
Compile-in X if (and only if) ARC is not in use. This is provided to handle obscure cases not covered by the other macros.

IF_NO_GC

Basic retain operation... calls [NSObject -retain]
Does nothing when ARC is in use.
Basic release operation... calls [NSObject -release]
Does nothing when ARC is in use.
Basic autorelease operation... calls [NSObject -autorelease]
Does nothing when ARC is in use.
Tested retain - only invoke the objective-c method if the receiver is not nil.
Does nothing when ARC is in use.
Tested release - only invoke the objective-c method if the receiver is not nil.
Does nothing when ARC is in use.
Tested autorelease - only invoke the objective-c method if the receiver is not nil.
Does nothing when ARC is in use.
ASSIGN(object,value) assigns the value to the object with appropriate retain and release operations.
Use this to avoid retain/release errors.
ASSIGNCOPY(object,value) assigns a copy of the value to the object with release of the original.
Use this to avoid retain/release errors.
ASSIGNMUTABLECOPY(object,value) assigns a mutable copy of the value to the object with release of the original.
Use this to avoid retain/release errors.
DESTROY() is a release operation which also sets the variable to be a nil pointer for tidiness - we can't accidentally use a DESTROYED object later. It also makes sure to set the variable to nil before releasing the object - to avoid side-effects of the release trying to reference the object being released through the variable.
DEALLOC calls the superclass implementation of dealloc, unless ARC is in use (in which case it does nothing).
ENTER_POOL creates an autorelease pool and places subsequent code in a block.
The block must be terminated with a corresponding LEAVE_POOL.
You should not break, continue, or return from such a block of code (to do so could leak an autorelease pool and give objects a longer lifetime than they ought to have. If you wish to leave the block of code early, you should ensure that doing so causes the autorelease pool outside the block to be released promptly (since that will implicitly release the pool created at the start of the block too).
LEAVE_POOL terminates a block of code started with ENTER_POOL.
Compile-in X if (and only if) ARC is not in use. This is provided to handle obscure cases not covered by the other macros.
DEPRECATED... use IF_NO_ARC() instead.

LEAVE_POOL

RECREATE_AUTORELEASE_POOL

Basic retain operation... calls [NSObject -retain]
Does nothing when ARC is in use.
Basic release operation... calls [NSObject -release]
Does nothing when ARC is in use.
Basic autorelease operation... calls [NSObject -autorelease]
Does nothing when ARC is in use.
Tested retain - only invoke the objective-c method if the receiver is not nil.
Does nothing when ARC is in use.
Tested release - only invoke the objective-c method if the receiver is not nil.
Does nothing when ARC is in use.
Tested autorelease - only invoke the objective-c method if the receiver is not nil.
Does nothing when ARC is in use.
ASSIGN(object,value) assigns the value to the object with appropriate retain and release operations.
Use this to avoid retain/release errors.
ASSIGNCOPY(object,value) assigns a copy of the value to the object with release of the original.
Use this to avoid retain/release errors.
ASSIGNMUTABLECOPY(object,value) assigns a mutable copy of the value to the object with release of the original.
Use this to avoid retain/release errors.
DESTROY() is a release operation which also sets the variable to be a nil pointer for tidiness - we can't accidentally use a DESTROYED object later. It also makes sure to set the variable to nil before releasing the object - to avoid side-effects of the release trying to reference the object being released through the variable.
DEALLOC calls the superclass implementation of dealloc, unless ARC is in use (in which case it does nothing).
ENTER_POOL creates an autorelease pool and places subsequent code in a block.
The block must be terminated with a corresponding LEAVE_POOL.
You should not break, continue, or return from such a block of code (to do so could leak an autorelease pool and give objects a longer lifetime than they ought to have. If you wish to leave the block of code early, you should ensure that doing so causes the autorelease pool outside the block to be released promptly (since that will implicitly release the pool created at the start of the block too).
LEAVE_POOL terminates a block of code started with ENTER_POOL.
Compile-in X if (and only if) ARC is not in use. This is provided to handle obscure cases not covered by the other macros.
DEPRECATED... use IF_NO_ARC() instead.
DEPRECATED... use ENTER_POOL and LEAVE_POOL and make sure your code does not break/continue/return out of the section of code.
DEPRECATED... use ENTER_POOL and LEAVE_POOL and make sure your code does not break/continue/return out of the section of code.

RELEASE

Basic retain operation... calls [NSObject -retain]
Does nothing when ARC is in use.
Basic release operation... calls [NSObject -release]
Does nothing when ARC is in use.

RETAIN

Basic retain operation... calls [NSObject -retain]
Does nothing when ARC is in use.

TEST_AUTORELEASE

TEST_RELEASE

TEST_RETAIN

Basic retain operation... calls [NSObject -retain]
Does nothing when ARC is in use.
Basic release operation... calls [NSObject -release]
Does nothing when ARC is in use.
Basic autorelease operation... calls [NSObject -autorelease]
Does nothing when ARC is in use.
Tested retain - only invoke the objective-c method if the receiver is not nil.
Does nothing when ARC is in use.
Tested release - only invoke the objective-c method if the receiver is not nil.
Does nothing when ARC is in use.
Tested autorelease - only invoke the objective-c method if the receiver is not nil.
Does nothing when ARC is in use.
ASSIGN(object,value) assigns the value to the object with appropriate retain and release operations.
Use this to avoid retain/release errors.
ASSIGNCOPY(object,value) assigns a copy of the value to the object with release of the original.
Use this to avoid retain/release errors.
ASSIGNMUTABLECOPY(object,value) assigns a mutable copy of the value to the object with release of the original.
Use this to avoid retain/release errors.
DESTROY() is a release operation which also sets the variable to be a nil pointer for tidiness - we can't accidentally use a DESTROYED object later. It also makes sure to set the variable to nil before releasing the object - to avoid side-effects of the release trying to reference the object being released through the variable.
DEALLOC calls the superclass implementation of dealloc, unless ARC is in use (in which case it does nothing).
ENTER_POOL creates an autorelease pool and places subsequent code in a block.
The block must be terminated with a corresponding LEAVE_POOL.
You should not break, continue, or return from such a block of code (to do so could leak an autorelease pool and give objects a longer lifetime than they ought to have. If you wish to leave the block of code early, you should ensure that doing so causes the autorelease pool outside the block to be released promptly (since that will implicitly release the pool created at the start of the block too).
LEAVE_POOL terminates a block of code started with ENTER_POOL.
Compile-in X if (and only if) ARC is not in use. This is provided to handle obscure cases not covered by the other macros.
DEPRECATED... use IF_NO_ARC() instead.
DEPRECATED... use ENTER_POOL and LEAVE_POOL and make sure your code does not break/continue/return out of the section of code.
DEPRECATED... use ENTER_POOL and LEAVE_POOL and make sure your code does not break/continue/return out of the section of code.

This function (macro) is a GNUstep extension.

_(@"My string to translate")

is basically equivalent to

NSLocalizedString(@"My string to translate", @"")

Alternatively you may define GS_LOCALISATION_BUNDLE to be the bundle to be used to prvide the localisation information.

Basic retain operation... calls [NSObject -retain]
Does nothing when ARC is in use.
Basic release operation... calls [NSObject -release]
Does nothing when ARC is in use.
Basic autorelease operation... calls [NSObject -autorelease]
Does nothing when ARC is in use.
Tested retain - only invoke the objective-c method if the receiver is not nil.
Does nothing when ARC is in use.
Tested release - only invoke the objective-c method if the receiver is not nil.
Does nothing when ARC is in use.
Tested autorelease - only invoke the objective-c method if the receiver is not nil.
Does nothing when ARC is in use.
ASSIGN(object,value) assigns the value to the object with appropriate retain and release operations.
Use this to avoid retain/release errors.
ASSIGNCOPY(object,value) assigns a copy of the value to the object with release of the original.
Use this to avoid retain/release errors.
ASSIGNMUTABLECOPY(object,value) assigns a mutable copy of the value to the object with release of the original.
Use this to avoid retain/release errors.
DESTROY() is a release operation which also sets the variable to be a nil pointer for tidiness - we can't accidentally use a DESTROYED object later. It also makes sure to set the variable to nil before releasing the object - to avoid side-effects of the release trying to reference the object being released through the variable.
DEALLOC calls the superclass implementation of dealloc, unless ARC is in use (in which case it does nothing).
ENTER_POOL creates an autorelease pool and places subsequent code in a block.
The block must be terminated with a corresponding LEAVE_POOL.
You should not break, continue, or return from such a block of code (to do so could leak an autorelease pool and give objects a longer lifetime than they ought to have. If you wish to leave the block of code early, you should ensure that doing so causes the autorelease pool outside the block to be released promptly (since that will implicitly release the pool created at the start of the block too).
LEAVE_POOL terminates a block of code started with ENTER_POOL.
Compile-in X if (and only if) ARC is not in use. This is provided to handle obscure cases not covered by the other macros.
DEPRECATED... use IF_NO_ARC() instead.
DEPRECATED... use ENTER_POOL and LEAVE_POOL and make sure your code does not break/continue/return out of the section of code.
DEPRECATED... use ENTER_POOL and LEAVE_POOL and make sure your code does not break/continue/return out of the section of code.

This function (macro) is a GNUstep extension.

_(@"My string to translate")

is basically equivalent to

NSLocalizedString(@"My string to translate", @"")

Alternatively you may define GS_LOCALISATION_BUNDLE to be the bundle to be used to prvide the localisation information.

This function (macro) is a GNUstep extension.

__(@"My string to translate")

is exactly the same as

GSLocalizedStaticString(@"My string to translate", @"")

It is useful when you need to translate an application very quickly. You would use it as follows for static strings:

NSString *message = __(@"Hello there");... more code... NSLog (_(messages));

But please note that when you use this macro, you are not taking advantage of comments for the translator, so consider using GSLocalizedStaticString instead when you need a comment.

GSBlocks macros

BLOCK_SCOPE

Defines a block type. Will work whether or not the compiler natively supports blocks.
Calls a block. Works irrespective of whether the compiler supports blocks.
Calls a block without arguments.

CALL_BLOCK

Defines a block type. Will work whether or not the compiler natively supports blocks.
Calls a block. Works irrespective of whether the compiler supports blocks.
Calls a block without arguments.

CALL_BLOCK_NO_ARGS

Defines a block type. Will work whether or not the compiler natively supports blocks.
Calls a block. Works irrespective of whether the compiler supports blocks.
Calls a block without arguments.

CALL_BLOCK_RET

Defines a block type. Will work whether or not the compiler natively supports blocks.
Calls a block. Works irrespective of whether the compiler supports blocks.
Calls a block without arguments.

CALL_BLOCK_RET_NO_ARGS

Defines a block type. Will work whether or not the compiler natively supports blocks.
Calls a block. Works irrespective of whether the compiler supports blocks.
Calls a block without arguments.

CALL_NON_NULL_BLOCK

Defines a block type. Will work whether or not the compiler natively supports blocks.
Calls a block. Works irrespective of whether the compiler supports blocks.
Defines a block type. Will work whether or not the compiler natively supports blocks.
Calls a block. Works irrespective of whether the compiler supports blocks.
Calls a block without arguments.
Defines a block type. Will work whether or not the compiler natively supports blocks.
Calls a block. Works irrespective of whether the compiler supports blocks.
Calls a block without arguments.

CALL_NON_NULL_BLOCK_NO_ARGS

Defines a block type. Will work whether or not the compiler natively supports blocks.
Calls a block. Works irrespective of whether the compiler supports blocks.
Calls a block without arguments.

DEFINE_BLOCK_TYPE

Defines a block type. Will work whether or not the compiler natively supports blocks.
Defines a block type. Will work whether or not the compiler natively supports blocks.
Calls a block. Works irrespective of whether the compiler supports blocks.
Calls a block without arguments.
Defines a block type. Will work whether or not the compiler natively supports blocks.
Calls a block. Works irrespective of whether the compiler supports blocks.
Calls a block without arguments.

DEFINE_BLOCK_TYPE_NO_ARGS

GSVersionMacros macros

GS_API_LATEST

Macro to check a defined GNUstep version number (GS_GNUSTEP_V) against the supplied arguments. Returns true if no GNUstep version is specified, or if ADD <= version < REM, where ADD is the version number at which a feature guarded by the macro was introduced and REM is the version number at which it was removed.

The version number arguments are six digit integers where the first two digits are the major version number, the second two are the minor version number and the last two are the subminor number (all left padded with a zero where necessary). However, for convenience you can also use the predefined constants... GS_API_NONE , GS_API_LATEST ,

Also see OS_API_VERSION

NB. If you are changing the API (eg adding a new feature) you need to control the visibility io the new header file code using
#if GS_API_VERSION(ADD,GS_API_LATEST)
where ADD is the version number of the next minor release after the most recent one.
As a general principle you should not change the API with changing subminor version numbers... as that tends to confuse people (though Apple has sometimes done it).

Macro to check a defined OpenStep/OPENSTEP/MacOS-X version against the supplied arguments. Returns true if no version is specified, or if ADD <= version < REM, where ADD is the version number at which a feature guarded by the macro was introduced and REM is the version number at which it was removed.

The version number arguments are six digit integers where the first two digits are the major version number, the second two are the minor version number and the last two are the subminor number (all left padded with a zero where necessary). However, for convenience you can also use any of several predefined constants... GS_API_NONE , GS_API_LATEST , GS_API_OSSPEC , GS_API_OPENSTEP , GS_API_MACOSX

Also see GS_API_VERSION

For OSX compatibility, this macro also supports the use of Apple's symbolic constants for version numbering. Their contants are currently four digit values (two digits for the major version, one for the minor, and one for the subminor).

GS_API_MACOSX

Also see OS_API_VERSION

The version number arguments are six digit integers where the first two digits are the major version number, the second two are the minor version number and the last two are the subminor number (all left padded with a zero where necessary). However, for convenience you can also use any of several predefined constants... GS_API_NONE , GS_API_LATEST , GS_API_OSSPEC , GS_API_OPENSTEP , GS_API_MACOSX

Also see GS_API_VERSION

A constant which is the lowest possible version number (0) so that when used as the removal version (second argument of the GS_API_VERSION or OS_API_VERSION macro) represents a feature which is not present in any version.
eg.
#if OS_API_VERSION (GS_API_NONE, GS_API_NONE)
denotes code not present in OpenStep/OPENSTEP/MacOS-X
A constant to represent a feature which is still present in the latest version. This is the highest possible version number.
eg.
#if OS_API_VERSION (GS_API_MACOSX, GS_API_LATEST)
denotes code present from the initial MacOS-X version onwards.
The version number of the initial OpenStep specification.
eg.
#if OS_API_VERSION (GS_API_OSSPEC, GS_API_LATEST)
denotes code present from the OpenStep specification onwards.
The version number of the first OPENSTEP implementation.
eg.
#if OS_API_VERSION (GS_API_OPENSTEP, GS_API_LATEST)
denotes code present from the initial OPENSTEP version onwards.
The version number of the first MacOS-X implementation.
eg.
#if OS_API_VERSION (GS_API_MACOSX, GS_API_LATEST)
denotes code present from the initial MacOS-X version onwards.

GS_API_NONE

Also see OS_API_VERSION

The version number arguments are six digit integers where the first two digits are the major version number, the second two are the minor version number and the last two are the subminor number (all left padded with a zero where necessary). However, for convenience you can also use any of several predefined constants... GS_API_NONE , GS_API_LATEST , GS_API_OSSPEC , GS_API_OPENSTEP , GS_API_MACOSX

Also see GS_API_VERSION

GS_API_OPENSTEP

Also see OS_API_VERSION

The version number arguments are six digit integers where the first two digits are the major version number, the second two are the minor version number and the last two are the subminor number (all left padded with a zero where necessary). However, for convenience you can also use any of several predefined constants... GS_API_NONE , GS_API_LATEST , GS_API_OSSPEC , GS_API_OPENSTEP , GS_API_MACOSX

Also see GS_API_VERSION

GS_API_OSSPEC

Also see OS_API_VERSION

The version number arguments are six digit integers where the first two digits are the major version number, the second two are the minor version number and the last two are the subminor number (all left padded with a zero where necessary). However, for convenience you can also use any of several predefined constants... GS_API_NONE , GS_API_LATEST , GS_API_OSSPEC , GS_API_OPENSTEP , GS_API_MACOSX

Also see GS_API_VERSION

GS_API_VERSION

Macro to check a defined GNUstep version number (GS_GNUSTEP_V) against the supplied arguments. Returns true if no GNUstep version is specified, or if ADD <= version < REM, where ADD is the version number at which a feature guarded by the macro was introduced and REM is the version number at which it was removed.

Also see OS_API_VERSION

GS_CLANG_MINREQ

Also see OS_API_VERSION

The version number arguments are six digit integers where the first two digits are the major version number, the second two are the minor version number and the last two are the subminor number (all left padded with a zero where necessary). However, for convenience you can also use any of several predefined constants... GS_API_NONE , GS_API_LATEST , GS_API_OSSPEC , GS_API_OPENSTEP , GS_API_MACOSX

Also see GS_API_VERSION

GS_DEPRECATED_FUNC

Also see OS_API_VERSION

The version number arguments are six digit integers where the first two digits are the major version number, the second two are the minor version number and the last two are the subminor number (all left padded with a zero where necessary). However, for convenience you can also use any of several predefined constants... GS_API_NONE , GS_API_LATEST , GS_API_OSSPEC , GS_API_OPENSTEP , GS_API_MACOSX

Also see GS_API_VERSION

GS_EXPOSE

Also see OS_API_VERSION

The version number arguments are six digit integers where the first two digits are the major version number, the second two are the minor version number and the last two are the subminor number (all left padded with a zero where necessary). However, for convenience you can also use any of several predefined constants... GS_API_NONE , GS_API_LATEST , GS_API_OSSPEC , GS_API_OPENSTEP , GS_API_MACOSX

Also see GS_API_VERSION

GS_GCC_MINREQ

Also see OS_API_VERSION

The version number arguments are six digit integers where the first two digits are the major version number, the second two are the minor version number and the last two are the subminor number (all left padded with a zero where necessary). However, for convenience you can also use any of several predefined constants... GS_API_NONE , GS_API_LATEST , GS_API_OSSPEC , GS_API_OPENSTEP , GS_API_MACOSX

Also see GS_API_VERSION

GS_NORETURN_METHOD

Also see OS_API_VERSION

The version number arguments are six digit integers where the first two digits are the major version number, the second two are the minor version number and the last two are the subminor number (all left padded with a zero where necessary). However, for convenience you can also use any of several predefined constants... GS_API_NONE , GS_API_LATEST , GS_API_OSSPEC , GS_API_OPENSTEP , GS_API_MACOSX

Also see GS_API_VERSION

GS_UNIMPLEMENTED

Also see OS_API_VERSION

The version number arguments are six digit integers where the first two digits are the major version number, the second two are the minor version number and the last two are the subminor number (all left padded with a zero where necessary). However, for convenience you can also use any of several predefined constants... GS_API_NONE , GS_API_LATEST , GS_API_OSSPEC , GS_API_OPENSTEP , GS_API_MACOSX

Also see GS_API_VERSION

GS_UNUSED_ARG

Also see OS_API_VERSION

The version number arguments are six digit integers where the first two digits are the major version number, the second two are the minor version number and the last two are the subminor number (all left padded with a zero where necessary). However, for convenience you can also use any of several predefined constants... GS_API_NONE , GS_API_LATEST , GS_API_OSSPEC , GS_API_OPENSTEP , GS_API_MACOSX

Also see GS_API_VERSION

GS_UNUSED_FUNC

Also see OS_API_VERSION

The version number arguments are six digit integers where the first two digits are the major version number, the second two are the minor version number and the last two are the subminor number (all left padded with a zero where necessary). However, for convenience you can also use any of several predefined constants... GS_API_NONE , GS_API_LATEST , GS_API_OSSPEC , GS_API_OPENSTEP , GS_API_MACOSX

Also see GS_API_VERSION

GS_UNUSED_IVAR

Also see OS_API_VERSION

The version number arguments are six digit integers where the first two digits are the major version number, the second two are the minor version number and the last two are the subminor number (all left padded with a zero where necessary). However, for convenience you can also use any of several predefined constants... GS_API_NONE , GS_API_LATEST , GS_API_OSSPEC , GS_API_OPENSTEP , GS_API_MACOSX

Also see GS_API_VERSION

MAC_OS_X_VERSION_MAX_ALLOWED

Also see OS_API_VERSION

The version number arguments are six digit integers where the first two digits are the major version number, the second two are the minor version number and the last two are the subminor number (all left padded with a zero where necessary). However, for convenience you can also use any of several predefined constants... GS_API_NONE , GS_API_LATEST , GS_API_OSSPEC , GS_API_OPENSTEP , GS_API_MACOSX

Also see GS_API_VERSION

NS_CONSUMED

Also see OS_API_VERSION

The version number arguments are six digit integers where the first two digits are the major version number, the second two are the minor version number and the last two are the subminor number (all left padded with a zero where necessary). However, for convenience you can also use any of several predefined constants... GS_API_NONE , GS_API_LATEST , GS_API_OSSPEC , GS_API_OPENSTEP , GS_API_MACOSX

Also see GS_API_VERSION

NS_CONSUMES_SELF

Also see OS_API_VERSION

The version number arguments are six digit integers where the first two digits are the major version number, the second two are the minor version number and the last two are the subminor number (all left padded with a zero where necessary). However, for convenience you can also use any of several predefined constants... GS_API_NONE , GS_API_LATEST , GS_API_OSSPEC , GS_API_OPENSTEP , GS_API_MACOSX

Also see GS_API_VERSION

NS_RETURNS_NOT_RETAINED

Also see OS_API_VERSION

The version number arguments are six digit integers where the first two digits are the major version number, the second two are the minor version number and the last two are the subminor number (all left padded with a zero where necessary). However, for convenience you can also use any of several predefined constants... GS_API_NONE , GS_API_LATEST , GS_API_OSSPEC , GS_API_OPENSTEP , GS_API_MACOSX

Also see GS_API_VERSION

NS_RETURNS_RETAINED

Also see OS_API_VERSION

The version number arguments are six digit integers where the first two digits are the major version number, the second two are the minor version number and the last two are the subminor number (all left padded with a zero where necessary). However, for convenience you can also use any of several predefined constants... GS_API_NONE , GS_API_LATEST , GS_API_OSSPEC , GS_API_OPENSTEP , GS_API_MACOSX

Also see GS_API_VERSION

OS_API_VERSION

Also see OS_API_VERSION

Macro to check a defined OpenStep/OPENSTEP/MacOS-X version against the supplied arguments. Returns true if no version is specified, or if ADD <= version < REM, where ADD is the version number at which a feature guarded by the macro was introduced and REM is the version number at which it was removed.

The version number arguments are six digit integers where the first two digits are the major version number, the second two are the minor version number and the last two are the subminor number (all left padded with a zero where necessary). However, for convenience you can also use any of several predefined constants... GS_API_NONE , GS_API_LATEST , GS_API_OSSPEC , GS_API_OPENSTEP , GS_API_MACOSX

Also see GS_API_VERSION

__has_feature

Also see OS_API_VERSION

The version number arguments are six digit integers where the first two digits are the major version number, the second two are the minor version number and the last two are the subminor number (all left padded with a zero where necessary). However, for convenience you can also use any of several predefined constants... GS_API_NONE , GS_API_LATEST , GS_API_OSSPEC , GS_API_OPENSTEP , GS_API_MACOSX

Also see GS_API_VERSION

GSObjCRuntime macros

GS_MAX_OBJECTS_FROM_STACK

The number of objects to try to get from varargs into an array on the stack... if there are more than this, use the heap. NB. This MUST be a multiple of 2

GS_USEIDLIST

The number of objects to try to get from varargs into an array on the stack... if there are more than this, use the heap. NB. This MUST be a multiple of 2

This is a macro designed to minimise the use of memory allocation and deallocation when you need to work with a vararg list of objects.
The objects are unpacked from the vararg list into two 'C' arrays and then a code fragment you specify is able to make use of them before that 'C' array is destroyed.

The firstObject argument is the name of the formal parameter in your method or function which precedes the ',...' denoting variable args.

The code argument is a piece of objective-c code to be executed to make use of the objects stored in the 'C' arrays.
When this code is called the unsigned integer '__count' will contain the number of objects unpacked, the pointer '__objects' will point to the first object in each pair, and the pointer '__pairs' will point to an array containing the second halves of the pairs of objects whose first halves are in '__objects'.
This lets you pack a list of the form 'key, value, key, value,...' into an array of keys and an array of values.

This is a macro designed to minimise the use of memory allocation and deallocation when you need to work with a vararg list of objects.
The objects are unpacked from the vararg list into a 'C' array and then a code fragment you specify is able to make use of them before that 'C' array is destroyed.

The firstObject argument is the name of the formal parameter in your method or function which precedes the ',...' denoting variable args.

The code argument is a piece of objective-c code to be executed to make use of the objects stored in the 'C' array.
When this code is called the unsigned integer '__count' will contain the number of objects unpacked, and the pointer '__objects' will point to the unpacked objects, ie. firstObject followed by the vararg arguments up to (but not including) the first nil.

GS_USEIDPAIRLIST

The number of objects to try to get from varargs into an array on the stack... if there are more than this, use the heap. NB. This MUST be a multiple of 2

The firstObject argument is the name of the formal parameter in your method or function which precedes the ',...' denoting variable args.

GSIMap macros

GS_PART_MAP_ENUMERATOR

Used to implement fast enumeration methods in classes that use GSIMap for their data storage.

NSDebug+GNUstepBase macros

ALog

NSDebugLLog() is the basic debug logging macro used to display log messages using NSLog() , if debug logging was enabled at compile time and the appropriate logging key was set at runtime.

Debug logging which can be enabled/disabled by defining GSDIAGNOSE when compiling and also setting values in the mutable set which is set up by NSProcessInfo. GSDIAGNOSE is defined automatically unless diagnose=no is specified in the make arguments.

NSProcess initialises a set of strings that are the names of active debug keys using the '--GNU-Debug=...' command line argument. Each command-line argument of that form is removed from NSProcessInfo 's list of arguments and the variable part (...) is added to the set. This means that as far as the program proper is concerned, it is running with the same arguments as if debugging had not been enabled.

For instance, to debug the NSBundle class, run your program with '--GNU-Debug=NSBundle' You can of course supply multiple '--GNU-Debug=...' arguments to output debug information on more than one thing.

NSUserDefaults also adds debug keys from the array given by the GNU-Debug default... but these values will not take effect until the +standardUserDefaults method is called... so they are useless for debugging NSUserDefaults itself or for debugging any code executed before the defaults system is used.

To embed debug logging in your code you use the NSDebugLLog() or NSDebugLog() macro. NSDebugLog() is just NSDebugLLog() with the debug key set to 'dflt'. So, to activate debug statements that use NSDebugLog() , you supply the '--GNU-Debug=dflt' argument to your program.

You can also change the active debug keys under your programs control - NSProcessInfo has a [-debugSet] method that returns the mutable set that contains the active debug keys - your program can modify this set.

Two debug keys have a special effect - 'dflt' is the key used for debug logs statements where no debug key is specified, and 'NoWarn' is used to *disable* warning messages.

As a convenience, there are four more logging macros you can use - NSDebugFLog() , NSDebugFLLog() , NSDebugMLog() and NSDebugMLLog() . These are the same as the other macros, but are specifically for use in either functions or methods and prepend information about the file, line and either function or class/method in which the message was generated.

This macro is a shorthand for NSDebugLLog() using the default debug key... 'dflt'
This macro is like NSDebugLLog() but includes the name and location of the function in which the macro is used as part of the log output.
This macro is a shorthand for NSDebugFLLog() using the default debug key... 'dflt'
This macro is like NSDebugLLog() but includes the name and location of the method in which the macro is used as part of the log output.
This macro is a shorthand for NSDebugMLLog() using then default debug key... 'dflt'
This macro saves the name and location of the function in which the macro is used, along with a short string msg as the tag associated with a recorded object.
This macro saves the name and location of the method in which the macro is used, along with a short string msg as the tag associated with a recorded object.
Macro to log a message only the first time it is encountered.
Not entirely thread safe... but that's not really important, it just means that it's possible for the message to be logged more than once if two threads call it simultaneously when it has not already been called.
Use this from inside a function. Pass an NSString as a format, followed by zero or more arguments for the format string. Example: GSOnceFLog(@"This function is deprecated, use another");
Macro to log a message only the first time it is encountered.
Not entirely thread safe... but that's not really important, it just means that it's possible for the message to be logged more than once if two threads call it simultaneously when it has not already been called.
Use this from inside a method. Pass an NSString as a format followed by zero or more arguments for the format string.
Example: GSOnceMLog(@"This method is deprecated, use another");

NSWarnLog() is the basic debug logging macro used to display warning messages using NSLog() , if warn logging was not disabled at compile time and the disabling logging level was not set at runtime.

Warning messages which can be enabled/disabled by defining GSWARN when compiling.

You can also disable these messages at runtime by supplying a '--GNU-Debug=NoWarn' argument to the program, or by adding 'NoWarn' to the user default array named 'GNU-Debug'.

These logging macros are intended to be used when the software detects something that it not necessarily fatal or illegal, but looks like it might be a programming error. eg. attempting to remove 'nil' from an NSArray, which the Spec/documentation does not prohibit, but which a well written program should not be attempting (since an NSArray object cannot contain a 'nil').

NB. The 'warn=yes' option is understood by the GNUstep make package to mean that GSWARN should be defined, and the 'warn=no' means that GSWARN should be undefined. Default is to define it.

To embed debug logging in your code you use the NSWarnLog() macro.

As a convenience, there are two more logging macros you can use - NSWarnFLog() , and NSWarnMLog() . These are specifically for use in either functions or methods and prepend information about the file, line and either function or class/method in which the message was generated.

This macro is like NSWarnLog() but includes the name and location of the function in which the macro is used as part of the log output.
This macro is like NSWarnLog() but includes the name and location of the method in which the macro is used as part of the log output.
The DLog macro is a less powerful but commonly used logging macro, defined here for convenience when porting code. It will tell you the function name and line number but not the file location. It performs unconditional logging but is only compiled in when the program is built with DEBUG defined.
The Alog macro is the same as the DLog macro, but is always compiled in to the code whether DEBUG is defined or not.

DLog

NSDebugLLog() is the basic debug logging macro used to display log messages using NSLog() , if debug logging was enabled at compile time and the appropriate logging key was set at runtime.

Two debug keys have a special effect - 'dflt' is the key used for debug logs statements where no debug key is specified, and 'NoWarn' is used to *disable* warning messages.

NSWarnLog() is the basic debug logging macro used to display warning messages using NSLog() , if warn logging was not disabled at compile time and the disabling logging level was not set at runtime.

Warning messages which can be enabled/disabled by defining GSWARN when compiling.

You can also disable these messages at runtime by supplying a '--GNU-Debug=NoWarn' argument to the program, or by adding 'NoWarn' to the user default array named 'GNU-Debug'.

NB. The 'warn=yes' option is understood by the GNUstep make package to mean that GSWARN should be defined, and the 'warn=no' means that GSWARN should be undefined. Default is to define it.

To embed debug logging in your code you use the NSWarnLog() macro.

GSOnceFLog

NSDebugLLog() is the basic debug logging macro used to display log messages using NSLog() , if debug logging was enabled at compile time and the appropriate logging key was set at runtime.

Two debug keys have a special effect - 'dflt' is the key used for debug logs statements where no debug key is specified, and 'NoWarn' is used to *disable* warning messages.

This macro is a shorthand for NSDebugLLog() using the default debug key... 'dflt'
This macro is like NSDebugLLog() but includes the name and location of the function in which the macro is used as part of the log output.
This macro is a shorthand for NSDebugFLLog() using the default debug key... 'dflt'
This macro is like NSDebugLLog() but includes the name and location of the method in which the macro is used as part of the log output.
This macro is a shorthand for NSDebugMLLog() using then default debug key... 'dflt'
This macro saves the name and location of the function in which the macro is used, along with a short string msg as the tag associated with a recorded object.
This macro saves the name and location of the method in which the macro is used, along with a short string msg as the tag associated with a recorded object.
Macro to log a message only the first time it is encountered.
Not entirely thread safe... but that's not really important, it just means that it's possible for the message to be logged more than once if two threads call it simultaneously when it has not already been called.
Use this from inside a function. Pass an NSString as a format, followed by zero or more arguments for the format string. Example: GSOnceFLog(@"This function is deprecated, use another");

GSOnceMLog

NSDebugLLog() is the basic debug logging macro used to display log messages using NSLog() , if debug logging was enabled at compile time and the appropriate logging key was set at runtime.

Two debug keys have a special effect - 'dflt' is the key used for debug logs statements where no debug key is specified, and 'NoWarn' is used to *disable* warning messages.

This macro is a shorthand for NSDebugLLog() using the default debug key... 'dflt'
This macro is like NSDebugLLog() but includes the name and location of the function in which the macro is used as part of the log output.
This macro is a shorthand for NSDebugFLLog() using the default debug key... 'dflt'
This macro is like NSDebugLLog() but includes the name and location of the method in which the macro is used as part of the log output.
This macro is a shorthand for NSDebugMLLog() using then default debug key... 'dflt'
This macro saves the name and location of the function in which the macro is used, along with a short string msg as the tag associated with a recorded object.
This macro saves the name and location of the method in which the macro is used, along with a short string msg as the tag associated with a recorded object.
Macro to log a message only the first time it is encountered.
Not entirely thread safe... but that's not really important, it just means that it's possible for the message to be logged more than once if two threads call it simultaneously when it has not already been called.
Use this from inside a function. Pass an NSString as a format, followed by zero or more arguments for the format string. Example: GSOnceFLog(@"This function is deprecated, use another");
Macro to log a message only the first time it is encountered.
Not entirely thread safe... but that's not really important, it just means that it's possible for the message to be logged more than once if two threads call it simultaneously when it has not already been called.
Use this from inside a method. Pass an NSString as a format followed by zero or more arguments for the format string.
Example: GSOnceMLog(@"This method is deprecated, use another");

NSDebugFLLog

NSDebugLLog() is the basic debug logging macro used to display log messages using NSLog() , if debug logging was enabled at compile time and the appropriate logging key was set at runtime.

To embed debug logging in your code you use the NSDebugLLog() or NSDebugLog() macro. NSDebugLog() is just NSDebugLLog() with the debug key set to 'dflt'. So, to activate debug statements that use NSDebugLog() , you supply the '--GNU-Debug=dflt' argument to your program.

Two debug keys have a special effect - 'dflt' is the key used for debug logs statements where no debug key is specified, and 'NoWarn' is used to *disable* warning messages.

NSDebugLLog() is the basic debug logging macro used to display log messages using NSLog() , if debug logging was enabled at compile time and the appropriate logging key was set at runtime.

Two debug keys have a special effect - 'dflt' is the key used for debug logs statements where no debug key is specified, and 'NoWarn' is used to *disable* warning messages.

This macro is a shorthand for NSDebugLLog() using the default debug key... 'dflt'
This macro is like NSDebugLLog() but includes the name and location of the function in which the macro is used as part of the log output.
This macro is a shorthand for NSDebugFLLog() using the default debug key... 'dflt'
This macro is like NSDebugLLog() but includes the name and location of the method in which the macro is used as part of the log output.
This macro is a shorthand for NSDebugMLLog() using then default debug key... 'dflt'
This macro saves the name and location of the function in which the macro is used, along with a short string msg as the tag associated with a recorded object.
This macro saves the name and location of the method in which the macro is used, along with a short string msg as the tag associated with a recorded object.

NSDebugFLog

NSDebugLLog() is the basic debug logging macro used to display log messages using NSLog() , if debug logging was enabled at compile time and the appropriate logging key was set at runtime.

Two debug keys have a special effect - 'dflt' is the key used for debug logs statements where no debug key is specified, and 'NoWarn' is used to *disable* warning messages.

NSDebugLLog() is the basic debug logging macro used to display log messages using NSLog() , if debug logging was enabled at compile time and the appropriate logging key was set at runtime.

Two debug keys have a special effect - 'dflt' is the key used for debug logs statements where no debug key is specified, and 'NoWarn' is used to *disable* warning messages.

NSDebugFRLog

NSDebugLLog() is the basic debug logging macro used to display log messages using NSLog() , if debug logging was enabled at compile time and the appropriate logging key was set at runtime.

Two debug keys have a special effect - 'dflt' is the key used for debug logs statements where no debug key is specified, and 'NoWarn' is used to *disable* warning messages.

NSDebugLLog() is the basic debug logging macro used to display log messages using NSLog() , if debug logging was enabled at compile time and the appropriate logging key was set at runtime.

Two debug keys have a special effect - 'dflt' is the key used for debug logs statements where no debug key is specified, and 'NoWarn' is used to *disable* warning messages.

NSDebugLLog

NSDebugLLog() is the basic debug logging macro used to display log messages using NSLog() , if debug logging was enabled at compile time and the appropriate logging key was set at runtime.

Two debug keys have a special effect - 'dflt' is the key used for debug logs statements where no debug key is specified, and 'NoWarn' is used to *disable* warning messages.

NSDebugLLog() is the basic debug logging macro used to display log messages using NSLog() , if debug logging was enabled at compile time and the appropriate logging key was set at runtime.

Two debug keys have a special effect - 'dflt' is the key used for debug logs statements where no debug key is specified, and 'NoWarn' is used to *disable* warning messages.

NSDebugLog

NSDebugLLog() is the basic debug logging macro used to display log messages using NSLog() , if debug logging was enabled at compile time and the appropriate logging key was set at runtime.

Two debug keys have a special effect - 'dflt' is the key used for debug logs statements where no debug key is specified, and 'NoWarn' is used to *disable* warning messages.

This macro is a shorthand for NSDebugLLog() using the default debug key... 'dflt'

NSDebugLLog() is the basic debug logging macro used to display log messages using NSLog() , if debug logging was enabled at compile time and the appropriate logging key was set at runtime.

Two debug keys have a special effect - 'dflt' is the key used for debug logs statements where no debug key is specified, and 'NoWarn' is used to *disable* warning messages.

NSDebugMLLog

NSDebugLLog() is the basic debug logging macro used to display log messages using NSLog() , if debug logging was enabled at compile time and the appropriate logging key was set at runtime.

Two debug keys have a special effect - 'dflt' is the key used for debug logs statements where no debug key is specified, and 'NoWarn' is used to *disable* warning messages.

NSDebugLLog() is the basic debug logging macro used to display log messages using NSLog() , if debug logging was enabled at compile time and the appropriate logging key was set at runtime.

Two debug keys have a special effect - 'dflt' is the key used for debug logs statements where no debug key is specified, and 'NoWarn' is used to *disable* warning messages.

NSDebugMLog

NSDebugLLog() is the basic debug logging macro used to display log messages using NSLog() , if debug logging was enabled at compile time and the appropriate logging key was set at runtime.

Two debug keys have a special effect - 'dflt' is the key used for debug logs statements where no debug key is specified, and 'NoWarn' is used to *disable* warning messages.

NSDebugLLog() is the basic debug logging macro used to display log messages using NSLog() , if debug logging was enabled at compile time and the appropriate logging key was set at runtime.

Two debug keys have a special effect - 'dflt' is the key used for debug logs statements where no debug key is specified, and 'NoWarn' is used to *disable* warning messages.

NSDebugMRLog

NSDebugLLog() is the basic debug logging macro used to display log messages using NSLog() , if debug logging was enabled at compile time and the appropriate logging key was set at runtime.

Two debug keys have a special effect - 'dflt' is the key used for debug logs statements where no debug key is specified, and 'NoWarn' is used to *disable* warning messages.

NSWarnFLog