Saturday, February 25, 2017, 7:59:55 AM, David E Jones wrote:
> These all sound like good changes, and clarify what is really going on.
(Basically, I'm decreasing code size and complexity before the more
interesting changes are started.)
> Removing object wrapping IMO is more important than
These all sound like good changes, and clarify what is really going on.
Removing object wrapping IMO is more important than removing the
*Template*Model* interfaces. These interfaces don't have the same runtime and
GC overhead as object wrapping and they can be nice for type checking to
In FM3, I propose removing some legacy complexity:
- Remove BeansWrapper, which is the super class of
DefaultObjectWrapper, and add its functionality directly to
DeafultObjectWrapper. That we have this class hierarchy has purely
historical reasons. (Even if FM2, using pure BeansWrapper is
