Ticket #6 (closed feature: fixed)

Opened 2 years ago

Last modified 2 years ago

Should all class objects be dynamic?

Reported by: lth Assigned to: anonymous
Type: feature Priority: major
Milestone: M0 Component: Proposals
Version: 4 Keywords:
Cc:

Description

Class itself is sealed, but all the builtin objects in E262 are dynamic. Should all class objects be dynamic? This would be unfortunate for usability, but legacy code requires it... specifically, “function Foo(){}; Foo.bar = 3;” is not legal in Tamarin but is required for web compatibility. We’d prefer user-defined classes be sealed with respect by default, but builtin E262 objects must be unsealed. Deferred until we can get Edwin’s opinion.

Wiki location => proposals:builtin_classes

Attachments

Change History

Changed 2 years ago by jeffdyer

  • status changed from new to closed
  • resolution set to fixed

Resolution: allow class object's to be dynamic for backward compatibility with ES3. There does not appear to be great inconvenience or risk in doing so.

Note: See TracTickets for help on using tickets.