<br><br><div class="gmail_quote">On Thu, Aug 6, 2009 at 7:46 PM, askoh <span dir="ltr"><<a href="mailto:askoh@askoh.com">askoh@askoh.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Thanks for the detailed article about making Squeak callable.<br>
<br>
Instead of having a monolithic vm, can we break squeak.exe into squeak2.exe<br>
and squeak2.dll? The squeak2.exe will do the complex multi threaded tasks<br>
and call squeak2.dll which is more passive and simple. The novelty here is<br>
that squeak2.dll can be callable by any *.exe in any language. I also<br>
believe squeak2.dll would be useful for parallel processing in multi-cores.<br>
Is this a good idea? Is it doable?</blockquote><div><br></div><div>Packaging as a split .exe/.dll is a prerequisite of being able to link to the VM and is trivial. The bulk of the work is in the asynchronous call-back machinery.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
<br>
Thanks,<br>
Aik-Siong Koh<br>
<font color="#888888">--<br>
View this message in context: <a href="http://www.nabble.com/step-through-VM-source-tp24678490p24857906.html" target="_blank">http://www.nabble.com/step-through-VM-source-tp24678490p24857906.html</a><br>
</font><div><div></div><div class="h5">Sent from the Squeak - Dev mailing list archive at Nabble.com.<br>
<br>
<br>
</div></div></blockquote></div><br>