[Vm-dev] Proposal | Clean-up source tree's *src folders

[Marcel Taeumel]

Hi all!

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:

/src/plugins -> (same)

/src/vm -> /src/vm.32bit.cog.v3
/stacksrc/vm -> /src/vm.32bit.stack.v3

/spurstacksrc/vm -> /src/vm.32bit.stack.spur
/spurstack64src/vm -> /src/vm.64bit.stack.spur
/spursrc/vm -> /src/vm.32bit.cog.spur
/spur64src/vm -> /src/vm.64bit.cog.spur
/spursistasrc/vm -> /src/vm.32bit.sista.spur
/spursista64src/vm -> /src/vm.64bit.sista.spur

/nsspurstacksrc/vm -> /src/newspeak.vm.32bit.stack.spur
/nsspurstack64src/vm -> /src/newspeak.vm.64bit.stack.spur
/nsspursrc/vm -> /src/newspeak.vm.32bit.cog.spur
/nsspur64src/vm -> /src/newspeak.vm.64bit.cog.spur


/spurlowcodestacksrc/vm -> /src/lowcode.vm.32bit.stack.spur
/spurlowcodestack64src/vm -> /src/lowcode.vm.64bit.stack.spur

/spurlowcodesrc/vm -> /src/lowcode.vm.32bit.cog.spur
/spurlowcode64src/vm -> /src/lowcode.vm.64bit.cog.spur


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.

Also, there would be a clear place for /src/vm.32bit.interpreter.v3 too :-)

Thoughts? Opinions? Objections?

Best,
Marcel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20210713/20b211e5/attachment.html>