« Bugzilla Issues Index
#790 — 12.6.3: "(This value is not used but the call may have side-effects.)"
- bug_id:
790
- creation_ts:
2012-10-11 11:28:00 -0700
- short_desc:
12.6.3: "(This value is not used but the call may have side-effects.)"
- delta_ts:
2012-10-26 15:34:32 -0700
- product:
Draft for 6th Edition
- component:
editorial issue
- version:
Rev 10: September 27, 2012 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
FIXED
- priority:
Normal
- bug_severity:
minor
- everconfirmed:
true
- reporter:
Michael Dyck
- assigned_to:
Allen Wirfs-Brock
- commentid:
1928
- comment_count:
0
- who:
Michael Dyck
- bug_when:
2012-10-11 11:28:44 -0700
In 12.6.3 "The for Statement",
under "Runtime Semantics: Labelled Evaluation",
rule 1 step 1.b says:
Let exprValue be GetValue(exprRef).
(This value is not used but the call may have side-effects.)
But 'exprValue' *is* used: it's passed to LoopContinues() (which certainly uses it), and it's possibly returned as the result of the algorithm.
So delete the parenthesized sentence.
- commentid:
2043
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2012-10-25 14:58:40 -0700
corrected in rev 11 editor's draft
- commentid:
2187
- comment_count:
2
- who:
Allen Wirfs-Brock
- bug_when:
2012-10-26 15:34:32 -0700
in October 26, 2012 release draft