This mail is an automated notification from the bugs tracker
of the project: GNUstep.
/**************************************************************************/
[bugs #9850] Latest Modifications:
Changes by:
Richard Frith-Macdonald <[EMAIL PROTECTED]>
'Date:
Tue 08/24/2004 at 05:20 (GMT)
What | Removed | Added
---------------------------------------------------------------------------
Resolution | None | Fixed
Status | Open | Closed
------------------ Additional Follow-up Comments ----------------------------
Fixed in CVS .. thanks.
/**************************************************************************/
[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: Fixed
Privacy: Public
Assigned to: None
Status: Closed
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.
Follow-up Comments
------------------
-------------------------------------------------------
Date: Tue 08/24/2004 at 05:20 By: Richard Frith-Macdonald <CaS>
Fixed in CVS .. thanks.
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/
_______________________________________________
Bug-gnustep mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/bug-gnustep
