It is also worth noting that Granny 2.x shipped out of the box with a generic C serializer that handled circular references, discriminated unions, endianness conversion, and version remapping for arbitrary data structures. And that was in 2002.
My guess is the main reason to avoid the interior pointer problem is just because it requires pre-traversal, so that does become a "hard" problem if you care about speed, I should think (at least if we are taking the "how difficult is this for a layperson to understand" metric).
-
-
Also now I am kind of off on a tangent of thinking about what the most efficient way is to make a system that handles interior pointers properly :) I feel like it requires two traversals. But I would love to be wrong about that.
-
If you always hit the outer container first, it seems do-able. I wonder if you can enforce that in some way by choosing breadth versus depth at certain points.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.