#3 is more like: primitive value vs. bare object Or primitive value vs. [something else] object
Where object is split not only into value object and identity objects, but bare (value) objects are another split. You get bare vs heap just as you get value vs identity as cleavage planes in the universe of objects. Also: Legacy primitives would not be objects in any case. But we can mock up classes to wrap and/or emulate them and even declare in the user model that these very special classes in some sense “are” the primitives. > On Jan 12, 2022, at 3:27 PM, Dan Smith <daniel.sm...@oracle.com> wrote: > > #3: > > primitive value vs. object
