archives

« Bugzilla Issues Index

#3116 — Loader Object and Loader Record should be unified

• bug_id: 3116
• creation_ts: 2014-08-11 14:26:00 -0700
• short_desc: Loader Object and Loader Record should be unified
• delta_ts: 2015-03-16 14:30:58 -0700
• product: Draft for 6th Edition
• component: deferred features
• version: Rev 26: July 18, 2014 Draft
• rep_platform: All
• op_sys: All
• bug_status: RESOLVED
• resolution: WONTFIX
• priority: Normal
• bug_severity: enhancement
• everconfirmed: true
• reporter: Jason Orendorff
• assigned_to: Allen Wirfs-Brock

---

• commentid: 9753
• comment_count: 0
• who: Jason Orendorff
• bug_when: 2014-08-11 14:26:41 -0700

Currently Loader Records and Loader Objects are one-to-one.

15.2.3.1 "Loader Records and Loader Objects" should just be "Loader Objects" and the fields of the Loader Record should be internal slots of the Loader Object.

15.2.3.1.1 "CreateLoaderRecord" should be inlined into its sole call site in 26.3.1.1.

---

• commentid: 9761
• comment_count: 1
• who: Allen Wirfs-Brock
• bug_when: 2014-08-12 08:32:39 -0700

(In reply to Jason Orendorff from comment #0)
> Currently Loader Records and Loader Objects are one-to-one.
>
> 15.2.3.1 "Loader Records and Loader Objects" should just be "Loader Objects"
> and the fields of the Loader Record should be internal slots of the Loader
> Object.
>
> 15.2.3.1.1 "CreateLoaderRecord" should be inlined into its sole call site in
> 26.3.1.1.

I've found it conceptually clearer and notationally simpler to handle complex internal state in this manner. It decouples the internal semantics from its ES reflection in terms of objects and reduces possibility of object semantics unintentionally leaking into the internal semantics.

It's really just architectural layering.

---

• commentid: 13754
• comment_count: 2
• who: Allen Wirfs-Brock
• bug_when: 2015-03-16 14:30:58 -0700

concerns old module spec.