From: Scott Woods (scottw_at_[hidden])
Date: 2003-05-26 16:41:59
> > my "toe-in-the-water" as far as pointers goes - another "nasty" if I
follow
> > your suggestion properly. Generally this is moving into an area that is
> > covered by OODBs and relational DBs. My simplification of what (I think)
> > you want would be some kind of "persistent object id"? Worked with
> > CORBA?
>
> Each pointed-to object would be associated with a unique ID. Pointers
> to that object would then be represented by that ID. Perhaps it would
> only work with Boost smart pointers.
>
template<> class persisted_pointer? Just kidding.
Generally like the [unique ID] idea. Have had some minor exposure to CORBA
and
it deals with the same issue pretty damn thoroughly. But CORBA is also
tackling a
bigger problem space - *persisted_pointer may be a dereference to an object
on
another machine that hasnt even been loaded yet. So maybe some extension to
current persistence stuff for a smaller problem space, is achievable and
worthwhile.
Will keep gnawing on that 1.
Thanks,
Scott