archives

« Bugzilla Issues Index

#3013 — [[Module]] isn't a Module object, its a ModuleLinkage Record

• bug_id: 3013
• creation_ts: 2014-07-20 11:36:00 -0700
• short_desc: [[Module]] isn't a Module object, its a ModuleLinkage Record
• delta_ts: 2014-10-14 15:18:03 -0700
• product: Draft for 6th Edition
• component: Modules
• version: Rev 26: July 18, 2014 Draft
• rep_platform: All
• op_sys: All
• bug_status: RESOLVED
• resolution: FIXED
• priority: Normal
• bug_severity: enhancement
• everconfirmed: true
• reporter: johnjbarton
• assigned_to: Allen Wirfs-Brock
• cc: ["dherman", "jorendorff", "samth"]

---

• commentid: 9408
• comment_count: 0
• who: johnjbarton
• bug_when: 2014-07-20 11:36:44 -0700

The definition in

15.2.3.2 Load Records and LoadRequest Objects

[[Module]] The Module object produced by this load, or undefined

compounds the confusion caused by the unfortunately ambiguous naming of [[Module]] and newModule().

As far as I can tell [[Module]] is a ModuleLinkage record, that is metatdata about a module created by 15.2.5.1.1 CreateModuleLinkageRecord. It includes a property `.module` set in 15.2.5.6 LinkDynamicModules. This property has the properties of a "Module Instance Object" which is not defined in the spec, but seem to be the type that should be returned by `newModule()`. In other words, "[[Module]].module" isA Module.

Changing the definition above to "The ModuleLinkage record produced by this load or undefined" would help a bit. Changing [[Module]] to [[ModuleLinkage]] would help dramatically. Then we could say "[[ModuleLinkage]].module isA Module".

---

• commentid: 10324
• comment_count: 1
• who: Allen Wirfs-Brock
• bug_when: 2014-10-11 17:39:31 -0700

fixed in rev28 editor's draft

---

• commentid: 10490
• comment_count: 2
• who: Allen Wirfs-Brock
• bug_when: 2014-10-14 15:18:03 -0700

fixed in rev28