« Bugzilla Issues Index
#2957 — 7.4.10 CreateCompoundIterator: Investigate to make CompoundIterator indistinguishable from ListIterator
- bug_id:
2957
- creation_ts:
2014-06-02 07:57:00 -0700
- short_desc:
7.4.10 CreateCompoundIterator: Investigate to make CompoundIterator indistinguishable from ListIterator
- delta_ts:
2014-07-19 18:10:05 -0700
- product:
Draft for 6th Edition
- component:
technical issue
- version:
Rev 25: May 22, 2014 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
FIXED
- priority:
Normal
- bug_severity:
enhancement
- everconfirmed:
true
- reporter:
André Bargull
- assigned_to:
Allen Wirfs-Brock
- commentid:
8791
- comment_count:
0
- who:
André Bargull
- bug_when:
2014-06-02 07:57:22 -0700
7.4.8 CreateListIterator (list)
7.4.10 CreateCompoundIterator ( iterator1, iterator2 )
The current set-up makes it possible for user code to detect the difference between CompoundIterator and ListIterator (by calling the `next()` from one iterator on a different iterator).
It should be investigated whether it's possible to hide this implementation detail from user code.
- commentid:
9159
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2014-07-11 14:47:18 -0700
fixed in rev26 editor's draft
these methods are now specified that they will only work on the specific object for which they were defined. They fail fast in that case so so you can't tell from the failure which kind of iterator it was.
- commentid:
9367
- comment_count:
2
- who:
Allen Wirfs-Brock
- bug_when:
2014-07-19 18:10:05 -0700
fixed in rev26