GNUstep - Tasks: task #10362, Match OSX behaviors where NSError...
You are not allowed to post comments on this tracker with your current authentication level.
task #10362: Match OSX behaviors where NSError is used
Submitter: | Richard Frith-Macdonald <CaS> | ||
Submitted: | Mon 03 May 2010 09:08:48 AM UTC | ||
Category: | Foundation | Should Start On: | Mon 03 May 2010 12:00:00 AM UTC |
Should be Finished on: | Fri 03 Dec 2010 12:00:00 AM UTC | Priority: | 5 - Normal |
Status: | None | Privacy: | Public |
Percent Complete: | 0% | Assigned to: | None |
Open/Closed: | Open | Effort: | 0.00 |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
No changes have been made to this item
OSX has added the NSError class and is increasingly adding methods which use this instead of producing exceptions. The GNUstep code largely leaves NSError return values unpopulated or minimally populated.
We need to go through the methods which use NSError, and ensure that at least the most common problems cause an NSError to be returned which matches the behavior on OSX.
It would be good to provide testcases for the testsuite at the same time.
Difficulty level of this is quite low ... suitable for newcomers to the project I'd think.