<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><div style='font-size:10pt;font-family:Verdana,Arial,Helvetica,sans-serif;'>That's very good, thanks.<br><br>I will give it a try.<br><br>Cordially,<br><br>tty<br><br><br><br><div id="1"><br>---- On Tue, 26 Nov 2013 14:30:53 -0800 <b>Nicolas Cellier<nicolas.cellier.aka.nice@gmail.com></b> wrote ---- <br></div><br><blockquote style="border-left: 1px solid #0000FF; padding-left: 6px; margin:0 0 0 5px"> <div dir="ltr">Of course, a nickname is something personal, but I suggest tty, if you have affinity with bare os and low level stuff, it's a good match ;)<br></div><div><br><br><div> 2013/11/26 gettimothy <span dir="ltr"><<a subj="" mailid="gettimothy%40zoho.com" href="mailto:gettimothy@zoho.com" target="_blank">gettimothy@zoho.com</a>></span><br><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br><u></u><div><div style="font-size:10pt;font-family:verdana,arial,helvetica,sans-serif">Thank you Eliot.<br><br>'Spaghetti Stack' I love it...<br><br>I want to get the standard VM under my belt first--walk before run and all that.<br> <br>t, tim, or timothy is fine. 't' is easier to type and will not conflict with Tim Rowledge<br><br><br>Cordially,<br><br>t<br><br><br>---- On Tue, 26 Nov 2013 13:26:33 -0800 <b>Eliot Miranda<<a subj="" mailid="eliot.miranda%40gmail.com" href="mailto:eliot.miranda@gmail.com" target="_blank">eliot.miranda@gmail.com</a>></b> wrote ---- <br> <br><blockquote style="border-left:1px solid #0000ff;padding-left:6px;margin:0 0 0 5px"> <div dir="ltr">Hi Tim(othy?).<br><div><br><br><br><div>On Tue, Nov 26, 2013 at 1:22 PM, gettimothy <span dir="ltr"><<a subj="" mailid="gettimothy%40zoho.com" href="mailto:gettimothy@zoho.com" target="_blank">gettimothy@zoho.com</a>></span> wrote:<br> <blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"> <br><u></u><div><div style="font-size:10pt;font-family:verdana,arial,helvetica,sans-serif"> Does Cog Interpreter state and cycle differ from the standard VM ?<br></div></div></blockquote><div><br></div><div>Yes. Quite a lot. The best overview is <a href="http://www.mirandabanda.org/cogblog/2009/01/14/under-cover-contexts-and-the-big-frame-up/" target="_blank">http://www.mirandabanda.org/cogblog/2009/01/14/under-cover-contexts-and-the-big-frame-up/</a>. Rationale for closures is in the posts named "Closure Overview" & "Closure Bytecodes". HTH.</div> <div><br></div><div> </div><blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div style="font-size:10pt;font-family:verdana,arial,helvetica,sans-serif"> <br>Details are not needed, just a heads up so that when I do get to Cog work, I make it a point to study them.<br><br>From the Blue Book, here is the definition of Interpreter State and Cycle:<br><br> Interpreter State:<br> 1. The CompiledMethod whose bytecodes ar being executed.<br> 2. The location of the next bytecode to be executed in that CompiledMethod: i.e its /instruction pointer/<br> 3. The receiver and arguments of the message that invoked the CompiledMethod.<br> 4. Any temporary variables needed by the CompiledMethod.<br> 5. a stack.<br><br> Interpreter Cycle:<br> 1. fetch the bytecode from the CompiledMethod indicated by the instruction pointer.<br> 2. Increment the instruction pointer.<br> 3. Perform the function specified by the bytecode.<br><br><br>thx.<br><br>t</div></div><br></blockquote></div><br><br clear="all"><div><br></div>-- <br>best,<div>Eliot</div> </div></div> </blockquote><br></div></div> <br></blockquote></div><br></div> </blockquote><br></div></body></html>