O$6.1.1: Problem with object references stored in list

Doug Easterbrook doug at artsman.com
Sun Mar 1 13:33:39 EST 2015

hi Greg:

I can't tell you if its a bug or not -- but I do recall that there is some comment in the release notes about doing object reference counting and then deallocating the reference when the object goes away.   The release note read-me says:

- Object references auto delete
Object references are now deleted automatically when they are no longer required in order to free up memory

that might be what is getting you -- this change in behaviour where your object is no longer existing -- the references may magically go too.

Doug Easterbrook
Arts Management Systems Ltd.
mailto:doug at artsman.com
Phone (403) 536-1205    Fax (403) 536-1210

> On Mar 1, 2015, at 9:10 AM, Grzegorz (Greg) Pasternak <grzegorz at niagara.com> wrote:
> I have the code that stores object reference in the list.  The list is stored in task variable that is instantiated in Startup.
> In the same library there is Remote task that is instantiated to handle HTTP request.
> Part of the request processing is to use object reference that has been created and is stored in the task variable.
> I have noticed that upon searching the list for stored object reference inside the task variable the object reference gets destroyed.
> As a result the returned object reference is NULL.
> The above mechanism is working pretty well in Omnis Studio 5.1.
> Has anybody observed the above behavior?
> The manual clearly states that object references can be stored in lists and reused unless explicitly deleted or library closed.
> Could it be that this is the new bug introduced in Studio 6.1.1 ?
> Regards;
> Greg
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com

More information about the omnisdev-en mailing list