Up

NSObject+GNUstepBase documentation

Authors

Richard Frith-Macdonald (rfm@gnu.org)

Copyright: (C) 2003-2010 Free Software Foundation, Inc.

Software documentation for the NSObject(GNUstepBase) informal protocol

NSObject(GNUstepBase)

Declared in:
GNUstepBase/NSObject+GNUstepBase.h
Availability: Not in OpenStep/MacOS-X

Description forthcoming.
Method summary

compare: 

- (NSComparisonResult) compare: (id)anObject;
Availability: Not in OpenStep/MacOS-X

WARNING: The -compare: method for NSObject is deprecated due to subclasses declaring the same selector with conflicting signatures. Comparision of arbitrary objects is not just meaningless but also dangerous as most concrete implementations expect comparable objects as arguments often accessing instance variables directly. This method will be removed in a future release.

isInstance 

- (BOOL) isInstance;
Availability: Not in OpenStep/MacOS-X

For backward compatibility only... use class_isMetaClass() on the class of the receiver instead.

makeImmutableCopyOnFail: 

- (id) makeImmutableCopyOnFail: (BOOL)force;
Availability: Not in OpenStep/MacOS-X

Transmutes the receiver into an immutable version of the same object and returns the result.
If the receiver is not a mutable object or cannot be simply transmuted, then this method either returns the receiver unchanged or, if the force flag is set to YES, returns an autoreleased copy of the receiver.
Mutable classes should override this default implementation.
This method is used in methods which are declared to return immutable objects (eg. an NSArray), but which create and build mutable ones internally.

notImplemented: 

- (id) notImplemented: (SEL)aSel;
Availability: Not in OpenStep/MacOS-X

Message sent when an implementation wants to explicitly exclude a method (but cannot due to compiler constraint), and wants to make sure it is not called by mistake. Default implementation raises an exception at runtime.

shouldNotImplement: 

- (id) shouldNotImplement: (SEL)aSel;
Availability: Not in OpenStep/MacOS-X

Message sent when an implementation wants to explicitly exclude a method (but cannot due to compiler constraint) and forbid that subclasses implement it. Default implementation raises an exception at runtime. If a subclass does implement this method, however, the superclass's implementation will not be called, so this is not a perfect mechanism.

subclassResponsibility: 

- (id) subclassResponsibility: (SEL)aSel;
Availability: Not in OpenStep/MacOS-X

Message sent when an implementation wants to explicitly require a subclass to implement a method (but cannot at compile time since there is no abstract keyword in Objective-C). Default implementation raises an exception at runtime to alert developer that he/she forgot to override a method.


Up