It was mentioned at the introduction of CALL WORKER that not needing global variables was somehow in the mix. Is C_Object the thing that enables this? In other words, have a WORKER with a $myGlobals object. As long as the WORKER is alive, that object is available to all methods.
Keith - CDI > On Jul 25, 2017, at 1:29 AM, Peter Bozek via 4D_Tech <[email protected]> > wrote: > > As I understand it, there is one 'heap' of objects, what means all objects > are IP (where by object I mean here data structures containing data). > Object variables are local, process or IP, but they are just references to > this global object heap. > > You mention that variables are something like pointers, I prefer to > consider them a references (like 'fifth object from the right') for the > following reason: > Objects are ref-counted. This means that each (global) object keeps count > how many variables (local, process and IP) is referencing this object. When > that count get to 0, object is deleted. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
