<br><br><div><span class="gmail_quote">On 7/25/06, <b class="gmail_sendername">Ge Wang</b> <<a href="mailto:gewang@cs.princeton.edu">gewang@cs.princeton.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
As Kassen mentioned, advancing<br>time in the parent shred will allow children to execute. If no time<br>advance is desired, me.yield() should work.</blockquote><div><br><br>Actually, what I meant was that at times advancing time can give the shred itself time to execute which I hold to be a bug.
<br><br>Still not at a chucking computer but;<br><br><<<"hello world">>>;<br>1::second => now;<br><<<"good bye cruel world">>>;<br>me.exit();<br><br>I believe this will result in the shred going to shred heaven without leaving it's goodbye note.
<br></div><br><br><<<"nice party">>>;<br>
1::second => now;<br>
<<<"hey, is it that time already?">>>;<br>1::ms => now;<br>
me.exit();<br><br>This one should be more polite.<br><br>Note that I only observed this once and that I'm not sure wether it could affect other comands as well as printing to the terminal.<br><br>I reported on this but I'm not sure it was ever officially on the bug list. Might have been fixed since then, might have been a odd exception that was never reproduced? I'd test this if I were at home.
<br><br>Kas.<br>
</div>