Well, as far as collections are concerned, foundation could (should?)
switch to the java.util style of allowing / using Java null values in
NSArrays and NSDicts.
As for other parts of EOF/WO which rely on NullValue, this might work
or it might not. Personally I remember having to explicitly use
NullValue only once (since EOF in many places auto-converts to null),
and even in that place I think it was possible to remake the
frameworks to accept null as a standard. Can't remember exactly where
that was...
Maybe there are other legitimate reasons for using the Java version
of NullValue (except for the Obj-C legacy), but I don't know what
they are...
F
On Oct 26, 2008, at 23:17, Lachlan Deck wrote:
Not sure there's much that can be done about this
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
