<br><br><div><span class="gmail_quote">On 11/15/07, <b class="gmail_sendername">Peter Todd</b> <<a href="mailto:chuck@xinaesthetic.net">chuck@xinaesthetic.net</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;">
Hello,<br><br>I think it's not so much a question of 'what a shred is', as a more general issue of the scope of variables that are declared within a function (ie, they are not accessible outside the scope of said function). I'm about to leave my house, and not feeling quite clear enough to explain more completely, but I hope that's enough to point you in the right direction.
</blockquote><div><br><br>Yes, I know variables declared within a function belong to that function and can't be adressed from the outside but member variables of *objects* can be adressed from the outside and when sporking the function becomes a object.
<br></div><br>With all due respect I do think there are some big questions here about "what a Shred is". I can execute the following;<br><br>------------------<br>Shred foo[3];<br><br>foo[0].exit();<br>------------------------
<br><br>This is quite mysterious to me, here a "Shred" (object) that's not a "shred" (sub-process) can "exit". Those two lines don't generate any errors, apparently they are fine but I have no idea what they do.
<br><br>Yours,<br>Kas.<br></div>