On Wed, Nov 30, 2016 at 2:43 PM, Peter Jakobsson <[email protected]> wrote:
> Yes - I noticed that that works in components as well. The problem is > heterogeneous behaviour: > > Consider 2 calls to exactly the same method but in different contexts: > > parseADDRESS($myAddressObject) <— host method > parseADDRESS($myAddressObject) <— component method > > In the 1st case, parseADDRESS behaves like a pointer passing, where > $myAddressObject will be modified. > In the 2nd case parseADDRESS behaves like a non-pointer, makes a copy of > the data and $myAddressObject will *not* be modified. > Doesn't this seem to be a function of variable scope? -- Douglas von Roeder 949-336-2902 ********************************************************************** 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] **********************************************************************
