Issue 62: Failure behavior for iterator operations (zz-collection) Source: (, ) Nature: Uncategorized Severity: Summary: Summary: What should be done for remove/replace/retrieve_element_set_to_next if the element cannot be deleted/replaced/retrieved? Resolution: Revised Text: Actions taken: July 24, 1996: received issue Discussion: End of Annotations:===== From geoff Wed Jul 24 12:33:16 1996 Received: by amethyst.omg.org (5.4R2.01/1.34) id AA18453; Wed, 24 Jul 1996 12:33:16 -0400 Date: Wed, 24 Jul 1996 12:33:16 -0400 From: geoff (Geoffrey Speare) Message-Id: <9607241633.AA18453@amethyst.omg.org> To: issue-logger@omg.org Subject: issues with CosCollection X-Omg-Issue: 62 From: Julio Garcia Subject: issues with CosCollection To: issues@omg.org Date: Fri, 19 Jul 1996 15:18:58 -0600 (MDT) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Hello, here is a list of problems, issues, and questions that I have encountered while prototyping CosCollection::Heap, CosCollection::Iterator, and CosCollection::HeapFactory. Contact me if you need clarification. -- Julio Garcia - julio@fc.hp.com - http://hpfcmdd.fc.hp.com/~julio/ - (970) 229-3168 - FAX (970) 229-7182 ---------------------------------------------------------------------- QUESTIONS remove_element_set_to_next - Incomplete spec What should be done if the element cannot be deleted (eg. iterator is const or in-between)? advance the iterator anyway? My implementation does so return TRUE if there are more elements anyway? My implementation does so replace_element_set_to_next - Incomplete spec What should be done if the element cannot be replaced (eg. iterator is const or in-between)? advance the iterator anyway? My implementation does so return TRUE if there are more elements anyway? My implementation does so retrieve_element_set_to_next - Incomplete spec What should be done if the element cannot be retrieve (eg. iterator is in-between)? advance the iterator anyway? My implementation does so set more to TRUE if there are more elements anyway? My implementation does so