On 16.04.2009 16:27 Uhr, neil.stansbury () redbacksystems ! com wrote:
> Axel (or anyone else),
> Could you clarify the semantics of the "truthValue" argument in calls to
> Are there any differences in its meaning in calls to hasAssertions() vs
> GetTargets() etc etc
> I had read it meant some kind of underlying permanency, but the
> somewhere else it meant a resource object could you clarify for me?
IIRC, and honestly, that's far fetched, as that stuff predates me, the
truth value is there to overwrite an existing arch in a read-only
datasource with a "non-existing arch" in another datasource, so that the
combined compound datasource would act like that arch doesn't exist.