<br><br><div class="gmail_quote">On Thu, Jun 9, 2011 at 8:38 AM, Andreas Raab <span dir="ltr"><<a href="mailto:andreas.raab@gmx.de">andreas.raab@gmx.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
On 6/9/2011 17:25, Igor Stasenko wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
On 9 June 2011 16:48, Andreas Raab<<a href="mailto:andreas.raab@gmx.de" target="_blank">andreas.raab@gmx.de</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 6/9/2011 16:19, Igor Stasenko wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Does it changes the way how svn checkout works?<br>
If i will checkout<br>
branches/Cog,<br>
will it do same as before,<br>
or i will need to do separate checkout of<br>
trunk/platforms/Cross/plugins?<br>
</blockquote>
Short answer: Try it :-)<br>
<br>
Longer answer: It doesn't change anything. Google svn:externals for more<br>
info.<br>
<br>
Cheers,<br>
- Andreas<br>
</blockquote>
So, with this change, the Cog and Squeak cross-platform plugins<br>
codebase are now same, right?<br>
</blockquote>
<br></div>
Yes, the Cross and the win32 plugin sources are now identical between interp and Cog branch.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This is good. Less things to worry about.<br>
</blockquote>
<br></div>
Indeed. The plan is to keep going incrementally until there are no differences left. At which point we might consider a slightly different layout of the sources for building interp, stackvm, and Cog side-by-side, but let's start with merging the support code first.<br>
</blockquote><div><br></div><div><br></div><div>Agreed. Looking forward, one thing we might want ot do is externalize the mapping of plugin classes to plugins. What I mean is that currently in VMMaker a plugin class can choose its plugin name, so that e.g. all of FFIPlugin ReentrantFFIPlugin ThreadedFFIPlugin ReentrantARMFFIPlugin ReentrantIA32FFIPlugin ReentrantPPCBEFFIPlugin ThreadedARMFFIPlugin ThreadedIA32FFIPlugin ThreadedPPCBEFFIPlugin have a moduleName of 'SqueakFFIPrims'. What this means is that the sources /can't/ contain the different plugins. So, a) I can't have one source tree containing code for different ISAs, x86, x86-64, PPC and ARM, and b) I can't have one source tree containing important variants such as ReentrantIA32FFIPlugin (for the non-thrreaded VM) and ThreadedIA32FFIPlugin (for the threaded VM). If instead, the mapping from class name to module name is done in the platforms tree and/or makefiles somehow, then there's no obstacle to doing what I want, which is include the threaded and non-threaded VMs side-by-side.</div>
<div><br></div><div>Anyway, just an issue to be addressed sometime, but not before sources are merged.</div><div><br></div><div>best,</div><div>Eliot</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Cheers,<br><font color="#888888">
- Andreas<br>
<br>
</font></blockquote></div><br>