Re: private scope data destruction, or GC; How it works?

[Olaf Till]

On Thu, Jan 19, 2017 at 04:22:38PM -0800, hale812 wrote:
> BTW, do CG deallocates all such arrays after exiting the function? I mean,
> if I make a copy of the output data with simple out=temp;, or "for
> i=1:length(temp); out(i)=temp(i);", should it be cleaned?

Only the returned arrays are kept, the others are cleaned. And a
simple copy with 'array2 = array1' does not need additional memory for
the data at all.

But as said, for the arrays that are kept, more memory then
corresponding to their data may be kept, if the arrays originate from
a larger array by an indexing operation. I'm not sure, but a
workaround that prevents this could be using a cat operation:

function returned_array = example_function ()

  large_array = rand (1, 1000000)

  small_array = large_array(1:1000);

  returned_array = horzcat (small_array, []);

endfunction

data = example_function (); # only necessary memory should be occupied

Olaf

-- 
public key id EAFE0591, e.g. on x-hkp://pool.sks-keyservers.net

signature.asc
Description: Digital signature