<div dir="ltr">Thanks Bill. I guess I was hoping reducing how much it had to scan over would make a scan faster, but am not correct. Do you have any suggestions for what one can do to cut GC times down on a code level when there is a lot of code going?<div><br></div><div>thanks</div><div>iain<br><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Apr 29, 2023 at 10:14 AM <<a href="mailto:bil@ccrma.stanford.edu">bil@ccrma.stanford.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">To keep an environment from the being garbage collected,<br>
assign it to a global variable -- as long as the variable<br>
holds the environment, it will be safe. This won't speed<br>
up the GC. It's possible to make s7 strings that are not<br>
seen at all by the GC (make_permament_string), but it's much<br>
trickier for an environment -- you'd have to be sure that<br>
every cell of every variable in the environment was<br>
permanent; otherwise the cell might have no one else<br>
referring to it, and the GC would free it.<br>
<br>
</blockquote></div>