Part of one day hands-on on Pharo

1. Runtime &
changes
S. Ducasse
http://www.pharo.org

2. Execution model
Virtual machine
Bytecode -> C-interpreter -> assembleur generated on
the fly

3. Files
VM (platform dependent)
.sources (all the sources of a distribution)
.changes (all your changes - a tape)
.image (all your binary objects)

4. “Image”
an image is a heap-dump
contains all the objects = all the system at a point in
time
nice and handy ***system cache***
Generally not a deployement artefact (advanced users)

5. Image/Change
Change1/Image1, ChangeX/ImageX
The system keeps them in sync
NB: VM can run without sources and changes (but you
will not be able to recognise your code :)

6. Changes
“changes” is a logging tape and cheap emergency tape
commit your changes to SmalltalkHub or (Git for
advanced users)

7. Development process
Define packages
Define project dependencies (Metacello configuration)
Save packages
Save project configurations
Define a CI job that automatically loads and verifies
everything