« Bugzilla Issues Index
#2757 — 8.1.1.1.6 GetBindingValue: Steps 2 and 3 contradict each other
- bug_id:
2757
- creation_ts:
2014-05-01 07:20:00 -0700
- short_desc:
8.1.1.1.6 GetBindingValue: Steps 2 and 3 contradict each other
- delta_ts:
2014-05-22 17:51:01 -0700
- product:
Draft for 6th Edition
- component:
technical issue
- version:
Rev 24: April 27, 2014 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
FIXED
- priority:
Normal
- bug_severity:
normal
- everconfirmed:
true
- reporter:
André Bargull
- assigned_to:
Allen Wirfs-Brock
- commentid:
8049
- comment_count:
0
- who:
André Bargull
- bug_when:
2014-05-01 07:20:16 -0700
8.1.1.1.6 GetBindingValue(N,S)
The condition in step 3 is never true per the assertion in step 2. Remove step 3?
- commentid:
8569
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2014-05-19 19:11:48 -0700
fixed in rev25 editor's draft.
I went look for a path where a Reference might get created for a binding that resolved to a deletable binding (created via a non-strict direct eval) which is then deleted(as a side-effect) before GetValue is performed on the Reference.
I couldn't find such a path.
- commentid:
8572
- comment_count:
2
- who:
André Bargull
- bug_when:
2014-05-20 02:13:20 -0700
(In reply to comment #1)
> I couldn't find such a path.
Maybe you meant bug 159? Such a path is possible in SetMutableBinding().
- commentid:
8595
- comment_count:
3
- who:
Allen Wirfs-Brock
- bug_when:
2014-05-22 17:51:01 -0700
fixed in rev25