Dynamic class default (was Re: Class method addition...)

Steven Johnson stejohns at adobe.com
Mon Apr 7 10:37:28 PDT 2008

> Making classes dynamic by default is likely to make the
> verifier -- what we previously called "strict mode" --
> less effective, because a reference o.x cannot be flagged
> as an error unless o is known to be an instance of a
> sealed class that doesn't have an 'x'; if classes are
> sealed by default then more errors will likely be caught
> early.

Dynamic classes also incur nontrivial overhead in memory use and runtime
performance. IMHO we'd want a fairly compelling argument for making all
classes dynamic by default.

More information about the Es4-discuss mailing list