Iterates over the objects of the receiver send each object valueForKey: with the parameter. The decimalValue of the returned object is accumalted and then divided by number of objects contained by the receiver as returned by [NSArray -coung] . An empty array returns NSDecimalNumber 0.

Description forthcoming.

Description forthcoming.

Description forthcoming.

Iterates over the objects of the receiver send each object valueForKey: with the parameter. The decimalValue of the returned object is accumalted. An empty array returns NSDecimalNumber 0.

EOKeyValueCoding protocol
This overrides NSObjects implementation of this method. Generally this method returns an array of objects returned by invoking [NSObject -valueForKey:] for each item in the receiver, substituting EONull for nil. Keys formated like "@function.someKey" are resolved by invoking [NSArray -computeFuncionWithKey:] "someKey" on the receiver. If the key is omitted, the function will be called with nil. The following functions are supported by default:

• @sum -> -computeSumForKey:
• @avg -> -computeAvgForKey:
• @max -> -computeMaxForKey:
• @min -> -computeMinForKey:
• @count -> -computeCountForKey:

Computational components generally expect a key to be passed to the function. This is not mandatory in which case 'nil' will be supplied. (i.e. you may use "@myFuncWhichCanHandleNil" as a key.) As a special case the key "count" does not actually invoke computeCountForKey: on receiver but returns the number of objects of the receiver.
There is no special handling of EONull. Therefore expect exceptions on EONull not responding to decimalValue and compare: when the are used with this mechanism.

EOKeyValueCoding protocol
Returns the object returned by invoking [NSObject -valueForKeyPath:] on the object returned by invoking [NSObject -valueForKey:] on the receiver with the first key component supplied by the key path, with rest of the key path.
If the first component starts with "@", the first component includes the key of the computational key component and as the form "@function.key". If there is only one key component, this method invokes [NSObject -valueForKey:] in the receiver with that component. Unlike the reference implementation GDL2 allows you to continue the keyPath in a meaningful way after @count but the path must then contain a key as the computational key structure implies. (i.e. you may use "@count.self.decimalValue") The actual key "self" is in fact ignored during the computation, but the formal structure must be maintained.
It should be mentioned that the reference implementation would return the result of "@count" independent of any additional key paths, even if they were meaningless like "@count.bla.strange". GDL2 will raise, if the object returned by valueForKey:@"count.bla" (which generally is an NSDecimalNumber) raises on valueForKey:@"strange".

Returns the object stored in the dictionary for this key. Unlike Foundation, this method may return objects for keys other than those explicitly stored in the receiver. These special keys are 'count', 'allKeys' and 'allValues'. We do not simply invoke [NSDictionary -valueForKey:] to avoid recursions in subclasses that might implement [NSDictionary -valueForKey:] by calling [NSDictionary -storedValueForKey:]

First checks whether the entire keyPath is contained as a key in the receiver before invoking super's implementation. (The special quoted key handling will probably be moved to a GSWDictionary subclass to be used by GSWDisplayGroup.)

Returns the object stored in the dictionary for this key. Unlike Foundation, this method may return objects for keys other than those explicitly stored in the receiver. These special keys are 'count', 'allKeys' and 'allValues'. We override the implementation to account for these special keys.

First checks whether the entire keyPath is contained as a key in the receiver before invoking super's implementation. (The special quoted key handling will probably be moved to a GSWDictionary subclass to be used by GSWDisplayGroup.)

Description forthcoming.

Description forthcoming.

Description forthcoming.

Description forthcoming.

Description forthcoming.

Description forthcoming.

Description forthcoming.

Unimplemented here. Relies on NSKeyValueCoding.

Does nothing. Key bindings are currently not cached so there is no need to flush them. This method exists for API compatibility.

Unimplemented here. Relies on NSKeyValueCoding.

Unimplemented here. Relies on NSKeyValueCoding.

Unimplemented here. Relies on NSKeyValueCoding.

Unimplemented here. Relies on NSKeyValueCoding.

Unimplemented here. Relies on NSKeyValueCoding.

Overrides the implementation of gnustep-base/Foundation this method is currently deprecated in favor of setValue:forKey: yet we aim to maintain WebObjects 4.5 compatibility.

This method is invoked by the EOKeyValueCoding mechanism when an attempt is made to set an null value for a scalar attribute. Contrary to the TOC of the documentation, this method is called unableToSetNilForKey: and not unableToSetNullForKey:
This implementation raises an NSInvalidArgument exception.
The NSKeyValueCoding -setNilValueForKey: is overriden to invoke this method instead. We manipulate the runtime to insure that our implementation of unableToSetNilForKey: is used in favor of the one in gnustep-base or Foundation.

Unimplemented here. Relies on NSKeyValueCoding.

Overrides the implementation of gnustep-base/Foundation this method is currently deprecated in favor of setValue:forKeyPath: yet we aim to maintain WebObjects 4.5 compatibility.

Overrides the implementation of gnustep-base/Foundation this method is currently deprecated in favor of setValue:forKeyPath: yet we aim to maintain WebObjects 4.5 compatibility.

Unimplemented here. Relies on NSKeyValueCoding.

Unimplemented here. Relies on NSKeyValueCoding.

Description forthcoming.