Re: [Somelib] Errors with downcasting using SOME::Object

[Thomas M. <tma...@ze...>]

John Palmieri wrote:

> Ok, now that i have that solved how do I create an object that does not get destroyed
> after the SOME::Object goes out of scope?  I don't want to keep track of more than one
> pointer per object loaded.  Is there a way of telling the SOME::Object not to delete
> pointers after it has gone out of scope (persistance)?

Not at this time.  I'm starting to think that we should collapse the heirarchy into
SOME::Object and provide a release method.

--
Thomas O Matelich
Senior Software Designer
Zetec, Inc.
sos...@us...
tma...@ze...