archives

« Bugzilla Issues Index

#1103 — 8.3.10.3: clarifying logic

• bug_id: 1103
• creation_ts: 2012-11-30 20:09:00 -0800
• short_desc: 8.3.10.3: clarifying logic
• delta_ts: 2012-12-21 18:08:37 -0800
• product: Draft for 6th Edition
• component: editorial issue
• version: Rev 12: November 22, 2012 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: 2923
• comment_count: 0
• who: Michael Dyck
• bug_when: 2012-11-30 20:09:41 -0800

In 8.3.10.3 "ValidateAndApplyPropertyDescriptor",
steps 2 and 3 are:
2. If current is undefined and extensible is false, then return false.
3. If current is undefined and extensible is true, then
...

If you combined them into:

2. If current is undefined, then
a. If extensible is false, then return false.
b. Else,
...

(or
2. If current is undefined, then
a. If extensible is false, then return false.
b. ...
)

then it would be slightly clearer that this chunk of pseudo-code completely handles the cases where current is undefined.

---

• commentid: 2932
• comment_count: 1
• who: Allen Wirfs-Brock
• bug_when: 2012-12-01 09:36:25 -0800

fixed in rev 13 editor's draft