<div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr">
Hi Eliot.<div><br></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">> I have no objection. The thing I object to is a deep hierarchy because it makes certain things difficult. The dog notation</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">> makes it easy to select specific types. If we’re going to do this I think we should also move all the build directories into</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">> a single build folder.</span><br style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">><br style="font-family: Arial, Helvetica, sans-serif;font-size: 13px"><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">> Now how? Do we reorganize and then fix or proceed incrementally?</span><br></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px"><br></span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">I am currently preparing a small changeset for VMMaker and the corresponding source tree in a fork:</span></div><div><span style="font-size: 10pt;font-family: Arial, Helvetica, sans-serif"><a href="https://github.com/marceltaeumel/opensmalltalk-vm/tree/marceltaeumel/src-cleanup/src">https://github.com/marceltaeumel/opensmalltalk-vm/tree/marceltaeumel/src-cleanup/src</a></span><br></div><div><br></div><div>Once I got this working (including build-dirs, no symlink :-), I would like to have a Zoom meeting. There we can double-check and directly merge it back upstream (both VMMaker and osvm). So you can also update your local working environment to see what breaks. :-D</div><div><br></div><div>Give me another day or two.</div><div><br></div><div>Best,</div><div>Marcel</div><div class="mb_sig"></div>
<blockquote class="history_container" type="cite" style="border-left-style: solid;border-width: 1px;margin-top: 20px;margin-left: 0px;padding-left: 10px;min-width: 500px">
<p style="color: #AAAAAA; margin-top: 10px;">Am 13.07.2021 18:02:17 schrieb Eliot Miranda <eliot.miranda@gmail.com>:</p><div style="font-family:Arial,Helvetica,sans-serif"><div dir="ltr"><br></div><div dir="ltr"><br><blockquote type="cite" style="min-width: 500px">On Jul 12, 2021, at 11:49 PM, Marcel Taeumel <marcel.taeumel@hpi.de> wrote:<br><br></blockquote></div><blockquote type="cite" style="min-width: 500px"><div dir="ltr"><span><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr">Hi all!<div class="mb_sig"></div><div><br></div><div>I would like to clarify (or re-arrange) the structure of the source tree so that we can continue to work on existing and experiment on new flavors of the VM. They would then better match our build structure:</div><div><br></div><div>/src/plugins -> (same)</div><div><br></div><div>/src/vm -> /src/vm.32bit.cog.v3</div><div>/stacksrc/vm -> /src/vm.32bit.stack.v3</div><div><br></div><div><div>/spurstacksrc/vm -> /src/vm.32bit.stack.spur</div><div>/spurstack64src/vm -> /src/vm.64bit.stack.spur</div></div><div>/spursrc/vm -> /src/vm.32bit.cog.spur</div><div>/spur64src/vm -> /src/vm.64bit.cog.spur</div><div><div>/spursistasrc/vm -> /src/vm.32bit.sista.spur</div><div>/spursista64src/vm -> /src/vm.64bit.sista.spur</div><div><br></div></div><div><div>/nsspurstacksrc/vm -> /src/newspeak.vm.32bit.stack.spur</div><div>/nsspurstack64src/vm -> /src/newspeak.vm.64bit.stack.spur</div></div><div>/nsspursrc/vm -> /src/newspeak.vm.32bit.cog.spur</div><div>/nsspur64src/vm -> /src/newspeak.vm.64bit.cog.spur<br></div><div><br></div><div><div><div>/spurlowcodestacksrc/vm -> /src/lowcode.vm.32bit.stack.spur</div><div>/spurlowcodestack64src/vm -> /src/lowcode.vm.64bit.stack.spur<br></div><div><div>/spurlowcodesrc/vm -> /src/lowcode.vm.32bit.cog.spur</div><div>/spurlowcode64src/vm -> /src/lowcode.vm.64bit.cog.spur<br></div><div><br></div></div></div><div>This would make 15 different *src folders disappear from the source tree's toplevel. Flavor-specific plugin lists might be defined from within VMMaker and generated into their respective src folders.</div><div><br></div><div>Also<span style="font-size: 10pt">, there would be a clear place for /src/vm.32bit.interpreter.v3 too :-)</span></div></div><div><br></div><div>Thoughts? Opinions? Objections?</div></div></span></div></blockquote><div><br></div>I have no objection. The thing I object to is a deep hierarchy because it makes certain things difficult. The dog notation makes it easy to select specific types. If we’re going to do this I think we should also move all the build directories into a single build folder.<div><br></div><div>Now how? Do we reorganize and then fix or proceed incrementally?<br><div><br><blockquote type="cite" style="min-width: 500px"><div dir="ltr"><span><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr"><div><br></div><div>Best,</div><div>Marcel</div></div></span></div></blockquote></div></div></div></blockquote></div>