Issue 769:  Page 17-29: OrderedCollection.remove_element_at_position (zz-collection)
Source:  (, )
Nature:  Revision
Severity:  Minor
Summary: Summary: Positions are numbered. When I remove 1 element, what happens with the indices?Do the portions of the indices of the elements located after the removed element decrement one?

Resolution: 
Revised Text: 
Actions taken:
September 29, 1997: received issue
Discussion: 

End of Annotations:=====
Return-Path: <geoff>
Date: Mon, 29 Sep 1997 10:04:55 -0400
From: Geoffrey Speare <geoff@omg.org>
To: issues
CC: Ringo.DeSmet@advalvas.be
Subject: [Ringo.DeSmet@advalvas.be: Object Collection Service: docs.]


Ringo,

I'm forwarding your message to issues@omg.org; from there, your
comments and
questions will be logged and forwarded to the group responsible for
updating
the Collection Service specification. 

Thanks for pointing these out!

Geoff Speare
OMG
geoff@omg.org

------- Start of forwarded message -------

5. page 17-29: OrderedCollection.remove_element_at_position:
     Positions are numbered. When I remove 1 element, what happens
     with the indices. Do the portion of the indices of the elements
     located after the removed element decrement by one?
        o If so, then the behaviour of the
          OrderedIterator.set_to_next_element() just resets the
          in-between state but doesn't increment the position, or an
          element is skipped during the iteration. As a side-effect,
          all iterators pointing to elements after the removed one,
          must decrement there position if they still want to point to
          the same element.
        o If not, then I have 'n' elements, with positions pointing to
          'n+1'. A call to e.g. retrieve_element_at_position(...)
          can't reference the 'n+1'-th element because the position is
          higher than the number of elements.