Follow-up Comment #2, bug #34744 (project gnustep): i'm not sure here as well.
throwing an exception sounds like the saner thing to do. on the other hand, this difference increases the porting effort from cocoa, e.g. in my case. i mainly opened the bug to make you aware of the difference. apple's documentation doesn't explicitly say they return NaN when the input is nil, but it also doesn't say that the method throws, and since, AFAIK, all throwing methods are documented, it is implicitly documented that it doesn't throw ;-) i can open a bug with apple that they should document that they return nil, but given my experience with opening bugs with them i expect them to act somewhere between 5 years from now and never. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?34744> _______________________________________________ Nachricht geschickt von/durch Savannah http://savannah.gnu.org/ _______________________________________________ Bug-gnustep mailing list Bug-gnustep@gnu.org https://lists.gnu.org/mailman/listinfo/bug-gnustep