bugGNUstep - Bugs: bug #9850, -getIndexes:maxCount:inIndexRange:...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

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

Submitted by:  -Deleted Account- <yjchen>
Submitted on:  Mon 02 Aug 2004 05:55:20 PM UTC  
 
Category: Base/FoundationSeverity: 3 - Normal
Item Group: Change RequestStatus: Fixed
Privacy: PublicAssigned to: None
Open/Closed: Closed

Tue 24 Aug 2004 05:20:56 AM UTC, comment #1:

Fixed in CVS .. thanks.

Richard Frith-Macdonald <CaS>
Project Member
Mon 02 Aug 2004 05:55:20 PM UTC, 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.

-Deleted Account- <yjchen>

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

Do you think this task is very important?
If so, you can click here to add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.

 

Please enter the title of George Orwell's famous dystopian book (it's a date):

 

 

Follow 2 latest changes.

Date Changed By Updated Field Previous Value => Replaced By
Tue 24 Aug 2004 05:20:56 AM UTCCaSStatusNone=>Fixed
  Open/ClosedOpen=>Closed

Back to the top


Powered by Savane 3.1-cleanup1