On Apr 11, 2006, at 19:03, Chip Salzenberg wrote:
1. "Value Model" for value objects
.... which is why saying 'stick with [ISNP]' is synonymous with 'no value types' [of that nature].
Ack. That's certainly an optimization thingy (e.g. native 'complex' type ...) and not targeted now.
2. "Reference Model" for value objects In Parrot, this mostly amounts to unique read-only PMCs. We'll have the read-only part, but the "unique" part, probably not.
Can I/we read this as: "morphing for Parrot core PMCs is history"? - Or in other words: differently sized PMCs (with a common (PObj) header) is the way to go?
The C<"unique" part> is, as already mentioned, rather orthogonal, but a nice to have, when it comes to hash lookups or shared MP items.
leo
