Re: NSArray.iterator and NSArray.listIterator bug

Tue, 20 Jun 2006 04:34:53 -0700

Sorry, I was a little misleading.  The Java 1.4.2 API for java.util.Enumeration says: 
"NOTE: The functionality of this interface is duplicated by the Iterator interface. In addition, Iterator adds an optional remove operation, and has shorter method names. New implementations should consider using Iterator in preference to Enumeration."  So the advice it to use Iterator, and there is nothing about not calling your method some crazy long name.  The only hint is that sun lists "has shorter method names" as a feature and benefit.

That being said, the Iterator could remove an element from the Iterator without removing it from the collection that provided the Iterator.  (i.e. a separate linked list where each element pointed to the an objectAtIndex(i) in the NSArray)  Still, the definition for remove in Iterator says "Removes from the underlying collection the last element returned by the iterator (optional operation).  This method can be called only once per call to next. The behavior of an iterator is unspecified if the underlying collection is modified while the iteration is in progress in any way other than by calling this method."  So it sounds like the behavior is a little confusing.

Nevertheless, it definitely doesn't work if there's a fault there at the to-many relationship.  Once the fault on the relationship is fired, then everything is fine.  So don't try to use it.  I have to file a bug report.

Kind regards,
John


On Jun 20, 2006, at 3:04 AM, Lachlan Deck wrote:

Hi there,

On 15/06/2006, at 8:22 PM, John Larson wrote:

objectEnumerator does work.  I didn't even think that that would be a different implementation except for Iterator's remove() method.  Oh well, just trying to obey Sun's advice about their Collections framework and not have to call methodWithAsLongANameAsPossible(). :-)

Late response but - I've never seen this advice. But, assuming the advice exists (or is it folklore?) then it'd be nice if Sun would remove all the 'get' prefixes from there class' methods. They certainly add clutter (I mean length) to the name of the method.

NSArray is immutable anyway - so the opportunity for remove() won't help unless it's a listIterator for a NSMutableArray.

with regards,
--

Lachlan Deck


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:

This email sent to [EMAIL PROTECTED]

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to