It seems I really do not need to worry too much because if I understood it correctly the memory of the variable at the end of the execution of that code is not only released but it is also deleted. Since the variable I am concerned about is used at the end of the code it does not exist after I use it because the code is finished and the memory is automatically freed and deleted.
JB > On Jan 3, 2020, at 12:58 PM, Bob Sneidar via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Well its really about what is going on under the hood. Memory dump for Macs > is not trivial from what I read. Apparently it involves turning off system > integrity and then booting into a special mode. At that point I stopped > reading. Not something I care to do with a production system. > > Bob S > > >> On Jan 3, 2020, at 11:58 , JB via use-livecode >> <use-livecode@lists.runrev.com> wrote: >> >> I have it figured out. >> >> You use it to delete each element of the array and >> that is the same as writing null to each element of >> the variable. >> >> I think they mean if you do not delete each element >> using this method all you are doing is putting empty >> into the variable and that would be the same as if >> you only write a null to the first element of the array. >> >> In other words putting empty into the variable is not >> secure. >> >> JB > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode