archives

« Bugzilla Issues Index

#4144 — "strict mode" vs "strict"

• bug_id: 4144
• creation_ts: 2015-03-08 14:32:00 -0700
• short_desc: "strict mode" vs "strict"
• delta_ts: 2015-03-17 16:57:06 -0700
• product: Draft for 6th Edition
• component: editorial issue
• version: Rev 35: March 4, 2015 Release Candidate 2
• rep_platform: All
• op_sys: All
• bug_status: RESOLVED
• resolution: FIXED
• priority: Normal
• bug_severity: normal
• everconfirmed: true
• reporter: Michael Dyck
• assigned_to: Allen Wirfs-Brock

---

• commentid: 13649
• comment_count: 0
• who: Michael Dyck
• bug_when: 2015-03-08 14:32:13 -0700

The spec is inconsistent on using "strict mode" vs just "strict". E.g.:

1 "strict mode binding" vs 4 "strict binding"
48 "strict mode code" vs 36 "strict code"
1 "strict mode variant" vs 6 "strict variant"

Personally, I'd say drop "mode":

(1) You don't need it.

(2) A one-word adjective is simpler than a two-word adjectival phrase.

(3) Phrases like "non-strict mode functions" read (at first glance) like
(non-strict) (mode functions)
rather than
non-(strict mode) functions

(4) To me, the strict variant doesn't seem like a 'mode' anyway.

---

• commentid: 13750
• comment_count: 1
• who: Allen Wirfs-Brock
• bug_when: 2015-03-16 12:58:38 -0700

fixed in rev36 editor's draft

"strict binding" is has a distinct meaning, separate from "strict mode". Eliminated the 1 occurrence of "strict mode binding"

"strict variant" is only used in 4.2.2. Eliminate the one occurrence of "strict mode variant"

In 9.2 defined the terms "strict function" and "non-strict" function

In 10.2.1 defined the term "non-strict code" meaning code that is not strict mode code.

Update rest of spec. text to use those terms.

---

• commentid: 13823
• comment_count: 2
• who: Allen Wirfs-Brock
• bug_when: 2015-03-17 16:57:06 -0700

in rev36