Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Time interval between the unix standard reference date
of 1 January 1970 and the OpenStep reference date of 1
January 2001
This number comes from:
(((31 years * 365 days) + 8 days for leap years) =
total number of days
24 hours * 60 minutes * 60
seconds)
This ignores leap-seconds.
Key for user info dictionary component which describes the error in a human readable format.
Domain for system errors (on MACH).
Domain for system errors.
Domain for system and system library errors.
Where one error has caused another, the underlying error can be stored in the user info dictionary uisng this key.
An exception when character set conversion fails.
A generic exception for general purpose usage.
An exception for caes where unexpected state is detected within an object
An exception used when an invalid argument is passed to a method or function.
An exception used when the system faols to allocate required memory.
An exception used when some form of parsing fails.
An exception used when an illegal range is encountered... usually this is used to provide more information than an invalid argument exception.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
For sets of pointer-sized or smaller quantities.
For sets of pointers hashed by address.
For sets of objects without retaining and releasing.
For sets of objects; similar to NSSet .
For sets of pointers with transfer of ownership upon insertion.
For sets of pointers to structs when the first field of the struct is the size of an int.
Description forthcoming.
Description forthcoming.
An exception for an unknown key
For keys that are pointer-sized or smaller quantities.
For values that are pointer-sized integer quantities.
For keys that are pointers not freed.
For values that are pointers not freed.
For keys that are pointers not freed, or 0.
For sets of objects without retaining and releasing.
For sets of objects without retaining and releasing.
For keys that are objects.
For values that are objects.
For keys that are pointers with transfer of ownership upon insertion.
For values that are pointers with transfer of ownership upon insertion.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Time interval difference between two dates, in seconds.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Type for enumerating.
NB. Implementation detail
... in GNUstep the layout must
correspond to that used by the GSIMap macros.
Hash table type... an opaque pointer to a data structure.
Callback functions.
hash... Hashing function.
NOTE: Elements with equal values must have equal hash
function values.
isEqual... Comparison
function.
retain... Retaining function
called when adding elements to the table.
release... Releasing function called when a data
element is removed from the table.
describe...
Description function.
Type for enumerating.
NB. Implementation detail
... in GNUstep the layout must
correspond to that used by the GSIMap macros.
Map table type... an opaque pointer to a data structure.
Callback functions for a key.
Comparison
function. Must not modify either key.
Retaining function called when adding elements to
table.
Notionally this must not modify the key
(the key may not actually have a retain count, or the
retain count may be stored externally to the key, but
in practice this often actually changes a counter within
the key).
Releasing function called when a data
element is removed from the table. This may decrease
a retain count or may actually destroy the key.
Description function. Generates a string
describing the key and does not modify the key
itsself.
Quantity that is not a key to the
map table.
Callback functions for a value.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Specifies the serialisation format for a serialised
property list.
NSPropertyListGNUstepFormat
extension of OpenStep format
NSPropertyListGNUstepBinaryFormat
efficient, hardware independent
NSPropertyListOpenStepFormat the
most human-readable format
NSPropertyListXMLFormat_v1_0
portable and readable
NSPropertyListBinaryFormat_v1_0 not
yet supported
Describes the mutability to use when generating
objects during deserialisation of a property list.
NSPropertyListImmutable all
objects in created list are immutable
NSPropertyListMutableContainers
dictionaries and arrays are mutable
NSPropertyListMutableContainersAndLeaves
dictionaries, arrays, strings and data objects
are mutable
The NSRange type is used to specify ranges of locations, typically items in an array, characters in a string, and bytes in a data object.
As 'boundary' or 'fencepost' errors are a particularly common problem in programming, it is important that you understand how an NSRange works.
An NSRange consists of a location and a length. The
points that are considered to lie in a range are the
integers from the location to the location plus
the length, so the number of points in a range is the
length of the range plus one.
However, if you
consider these points like the marks on a ruler,
you can only store information between
points. So the number of items that can be stored
in a range is the length of the range.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Enable/disable object deallocation.
If zombies are enabled, objects are by default not deallocated, and memory leaks. The NSDeallocateZombies variable lets you say that the the memory used by zombies should be freed.
Doing this makes the behavior of zombies similar to that when zombies are not enabled... the memory occupied by the zombie may be re-used for other purposes, at which time the isa pointer may be overwritten and the zombie behavior will cease.
The default value of this boolean is NO
, but
this can be controlled by the NSDeallocateZombies
environment variable.
Enable/disable zombies.
When an object is deallocated, its isa pointer is normally modified to the hexadecimal value 0xdeadface, so that any attempt to send a message to the deallocated object will cause a crash, and examination of the object within the debugger will show the 0xdeadface value... making it obvious why the program crashed.
Turning on zombies changes this behavior so that the isa pointer is modified to be that of the NSZombie class. When messages are sent to the object, intead of crashing, NSZombie will use NSLog() to produce an error message. By default the memory used by the object will not really be freed, so error messages will continue to be generated whenever a message is sent to the object, and the object instance variables will remain available for examination by the debugger.
The default value of this boolean is NO
, but
this can be controlled by the NSZombieEnabled
environment variable.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Retaining function called when adding elements to
table.
Notionally this must not modify the
element (the element may not actually have a retain
count, or the retain count may be stored externally to
the element, but in practice this often actually changes
a counter within the element).
Releasing function
called when a data element is removed from the table.
This may decrease a retain count or may actually destroy
the element.
Description function. Generates a
string describing the element and does not modify the
element itsself.
Description forthcoming.
A variable holding the file descriptor to which
NSLogv()
messages are written by default. GNUstep initialises
this to stderr.
You may change this, but for
thread safety should use the lock provided by
GSLogLock()
to protect the change.
A pointer to a function used to actually write the log data.
GNUstep initialises this to a function implementing the standard behavior for logging, but you may change this in your program in order to implement any custom behavior you wish. You should use the lock returned by GSLogLock() to protect any change you make.
Calls from NSLogv() to the function pointed to by this variable are protected by a lock, and should therefore be thread safe.
This function should accept a single NSString argument and return void.
The default implementation in GNUstep performs as follows -
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.
Description forthcoming.