archives

« Bugzilla Issues Index

#2523 — 13.11.5: suggested restructuring

• bug_id: 2523
• creation_ts: 2014-02-11 10:42:00 -0800
• short_desc: 13.11.5: suggested restructuring
• delta_ts: 2014-06-01 20:55:19 -0700
• product: Draft for 6th Edition
• component: editorial issue
• version: Rev 22: January 20, 2014 Draft
• rep_platform: All
• op_sys: All
• bug_status: RESOLVED
• resolution: FIXED
• priority: Normal
• bug_severity: enhancement
• everconfirmed: true
• reporter: Michael Dyck
• assigned_to: Allen Wirfs-Brock

---

• commentid: 7244
• comment_count: 0
• who: Michael Dyck
• bug_when: 2014-02-11 10:42:10 -0800

In 13.11.5 "Runtime Semantics: CaseBlockEvaluation":

13.11.5 / group 1

I suggest restructuring steps 4 and 5 to:

Repeat, letting C be each CaseClause in A
If /searching/ is *true*, then
[steps 4.b - 4.e]
else
[step 5.b]
Return NormalCompletion(/V/).

Reasons:

-- Currently, steps 4.a and 5.a say "Let C be the next CaseClause in A. ..."
I think these are the only points where an algorithm asks for the
'next' element in a List, as if the List carries around a cursor.
Eliminating them simplifies the implicit data model for Lists.

-- It's more obvious that each CaseClause in A is being processed exactly
once (modulo an early return via ReturnIfAbrupt).

-- It makes this algorithm closer in structure to (the first 4 steps of)
the algorithm in group 2. (And you could easily make them even closer.)

---

• commentid: 8329
• comment_count: 1
• who: Allen Wirfs-Brock
• bug_when: 2014-05-12 09:44:06 -0700

fixed in rev25 editor's draft

---

• commentid: 8780
• comment_count: 2
• who: Michael Dyck
• bug_when: 2014-06-01 20:55:19 -0700

confirmed fixed.