opencog-dev team mailing list archive

[Ari Heljakka <ari.heljakka@xxxxxxxxxxxxxx>]

> In the short term that might be a sensible approach to get it working
> and check that the port generally works (although I'm not sure if this
> will mess up the AtomSpace's index system). Long term however, we'll
> still want to ensure that the AtomSpace is consistent.

Sure, but as in NM codebase, the optimal solution seems to be that you 
offer this option to users but put a warning sign which urges people to 
understand that you can't use it in production code.

> If it assumes this, how does it ensure it gets the correct
> node/link/TruthValue back? Since the getHandle method returns a single
> atom, but there may be more than one atom that matches the getHandle
> parameters (since fresh=true overrides the check to make sure atoms
> are unique). Or if PLN uses getHandleSet instead and retrieves a
> number matching handles (thus getting around only singular results
> being returned), how does it work out which specific handle and thus
> which TV to use?
>
> ... actually, I just realised that one can simply follow the outgoing
> links of the root and trace along the tree. So I'm assuming this is
> how the outgoing tree is fetched?

Exactly.

> Right, since all adds under a given tree need to have the same version
> I'll have to think some more about this, and then look at the code
> more. Actually, since I'm essentially replacing Handles with
> pair<Handle,VersionHandle> in Vertex (and thus vtree), it should be
> possible to easily find the context of a tree before performing an
> add. In fact, would it be possible to use the root atom of each tree
> as the context?

My intuitive understanding of contexts is insufficient to answer that 
question.

-A