[Vm-dev] reorganizing opensmalltalk-vm

Eliot Miranda eliot.miranda at gmail.com
Thu Oct 25 17:30:44 UTC 2018


Hi All,

    efforts are underway to include the VMMaker source in the
opensmalltalk-vm repository.  I'm hoping to see all the Smalltalk source
included in the Tonel format (one file per class, and one file per extended
class), with support for Pharo and Squeak quite soon.  This is therefore an
opportunity to also reorganize the structure of the repository to have a
more comprehensible and less cluttered top-level directory.  I'm interested
in people's ideas.  here are two suggestions.

1. move all source under src and all builds under build. So
    src/smalltalk/                  all the VMMaker-related packages
                        AioPlugin
                        BytecodeSets
                        Cog
                        VMMaker
    src/generated/              all the generated code
                        plugins/     all generated plugins
                        v3              the V3 VM (now src/vm)
                        spur32       the 32-bit Spur VM (now spursrc/vm)
                        spur64       the 64-bit Spur VM (now spur64src/vm)
    src/platforms                 the current platforms directory
    src/third-party/
                        processors
    build/                             the current build directories
        macos32x86
        macos64x64
    deploy/
    image/
    tests/

2. single top-level directories for generated source, and Smalltalk source,
everything else unchanged
smalltalksrc/             all the VMMaker-related packages
generatedsrc/           all the generated code as above in src/generated,
but in generatedsrc instead
platforms
processors
third-party
tests
deploy

Obviously #1 is more work but produces a much cleaner structure.  Other
suggestions? Reactions to the above?
_,,,^..^,,,_
best, Eliot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20181025/91fb5ad8/attachment.html>


More information about the Vm-dev mailing list