Follow-up Comment #1, bug #34744 (project gnustep):
I have a problem with this one ...
Unless you know better, the behavior for this case is simply undocumented, and
OSX usual action when passed an invalid argument (and it's pretty hard to
argue that passing a non-date to a method which specifically says it expects a
date is anything other than an application error) is to raise an
NSInvalidArgumentException.
But ... we generally try to mirror Apple's current implementation, so maybe we
should simply remove the check for an invalid argument here (and replace it if
necessary later if/when Apple changes OSX)?
Have you tried reporting it as a bug to Apple? Most likely they'd say the
behavior is simply undefined, but they might decide to change it.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?34744>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
Bug-gnustep@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gnustep
