<br><br><div class="gmail_quote">On Sun, Mar 1, 2009 at 9:20 PM, Craig Latta <span dir="ltr"><<a href="mailto:craig@netjam.org">craig@netjam.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
[snip]<br>
As for whether to produce an object memory statically and then set it running, or transform an object memory which is always running... I think the resulting memory will need to load modules live anyway, so one might as well do all the transformations that way. Perhaps this is simply an aesthetic choice.</blockquote>
<div><br></div><div>Surely repeatability mandates that one roduce an object memory statically and then set it running? Because of things like delays the always running memory is almost never in a predictable state, so one always ends up with different bits even if they represent the same functionality.</div>
<div><br></div><div>E.</div><div></div></div>