------_=_NextPart_000_01BF4899.A28447BC
Content-Type: text/plain


The attached change set changes OrderedCollection>>removeIndex: so it
answers the element being removed, which appears to be the desired behavior.
I trekked through the image, looking at the senders of removeIndex: and all
of its senders, and couldn't find any code which seemed to expect to have
the collection answered instead of the element being removed.

 <<OrderedCollection-removeIndex# changes.17Dec903am.cs>> 

Bob Jarvis
Compuware @ Timken

> -----Original Message-----
> From:	Stefan Matthias Aust [SMTP:sma at 3plus4.de]
> Sent:	Thursday, December 16, 1999 3:42 PM
> To:	squeak at cs.uiuc.edu
> Subject:	[BUG?] removeAt: doesn't return object
> 
> In 2.6, removeAt: of OrderedCollection doesn't return the removed element
> as it would be useful but returns the receiver. IMHO this should be
> changed
> to conform with other remove methods.  The best place to change would be
> #removeIndex.  This change could also simplify #remove:ifAbsent: then.
> 
> bye
> --
> Stefan Matthias Aust  //  Bevor wir fallen, fallen wir lieber auf.

------_=_NextPart_000_01BF4899.A28447BC
Content-Type: text/plain; name="OrderedCollection-removeIndex# "
 ; x-mac-type="65417070"
 ; x-mac-creator="43534F6D"
Content-Disposition: attachment; filename="OrderedCollection-removeIndex# "
Content-Transfer-Encoding: imap_stub

0,2451,2,522,0,

------_=_NextPart_000_01BF4899.A28447BC--