ESTK keeps the entire session in Memory?

[DBarranca]

Hi,

apparently every script that you launch in ESTK is kept in memory - I wonder if this is designed.

As an example (there is more in this topic) create two separate script files, and run the first, then the second, against ESTK:

The first file:

var first = new Object();
$.writeln(typeof first); // object

and the second file:

var second = new Object();
$.writeln(typeof first); // object

Of course the second should say "undefined". To doublecheck that I've not poisoned the global space, I've tried:

$.writeln($.global.toSource()); // ({})

Unless you reboot ESTK, the all the vars are kept in memory no matter what script you're working on - except you explicitely set them to null or undefined.

I've run into this behavior casually - is it documented somewhere os should we file a bug?

Thanks

Davide Barranca

www.davidebarranca.com

[Michael_L_Hale]

The link you posted is not valid.

I have not seen that documented( not surprising ) and I am not sure it is a bug. If you choose the Debug-Reset menu before running you script it seems to clear any previously defined variables.

[DBarranca]

Apparently I'm unable to edit my own post to fix the link - here it is:

http://www.ps-scripts.com/bb/viewtopic.php?f=2&t=5517&sid=21455c36873ab898faf2597a785d08da