[bugs #9850] -getIndexes:maxCount:inIndexRange: (NSIndexSet) won't accept null NSRangePointer

[Yen-Ju Chen]

This mail is an automated notification from the bugs tracker
 of the project: GNUstep.




/**************************************************************************/
[bugs #9850] Full Item Snapshot:

URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=9850>
Project: GNUstep
Submitted by: Yen-Ju Chen
On: Mon 08/02/2004 at 17:55

Category:  Base/Foundation
Severity:  5 - Average
Item Group:  Change Request
Resolution:  None
Assigned to:  None
Status:  Open


Summary:  -getIndexes:maxCount:inIndexRange: (NSIndexSet) won't accept null 
NSRangePointer

Original Submission:  In Cocoa, NSIndexSet accept NULL pointer for 
NSRangePointer in -getIndexes:maxCount:inIndexRange: and get the indexes from 
all range.
In GNUstep, a NSException is raised.
Though the Cocoa document doesn't say about NULL NSRangePointer,
I think it is more convenient to use NULL to get indexes from all range.
Otherwise, indexRange has to be calculated every time in order to get all 
indexes, 
which is kind of troublesome.











For detailed info, follow this link:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=9850>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/