bruce-patel
Uploaded by
7 SLIDES
226 VUES
80LIKES

Understanding Smalltalk Run-Time Architecture: Key Concepts and Best Practices

DESCRIPTION

This overview provides insight into the Smalltalk Run-Time Architecture, focusing on the Virtual Machine, bytecode, and the importance of using the change file. It highlights best practices such as never editing source files manually, consistently saving code with Smalltalk, and the role of packages like parcels for efficient code management. The guide emphasizes that while bytecode is interpreted by the VM, the source and changes are essential during development but removed during deployment. Understanding these elements is crucial for maintaining robust Smalltalk applications.

1 / 7

Télécharger la présentation

Understanding Smalltalk Run-Time Architecture: Key Concepts and Best Practices

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Run-Time...

  2. Smalltalk Run-Time Architecture • Virtual Machine + Image + Changes and Sources • Image = bytecodes • Sources and changes = code (text)

  3. Does and Dont • Do not edit the source files by hand • Do not lose your change file (it contains your code) • You cannot lose code (if you keep the change file) • Always use Smalltalk to save your code • Always use Smalltalk to rename your environment

  4. All your changes are recorded • So have a lot at the changes sorter and change recovery tools suite of your dialect. • You should not lose code.

  5. Smalltalk Run-Time Architecture • The byte-code is in fact translated into native code by a just-in-time compiler (in VW, ST/X) • The source and the changes are not necessary for interpreting the byte-code, this is just for the development. Normally they are removed for deployment. • An application can be delivered as some byte-code files that will be executed with a VM. The development image is stripped to remove the unnecessary development components.

  6. VWorks Smalltalk Run-Time Architecture

  7. VWorks Runtime Architecture • Parcels reproduce the schema of the image and change: *.pcl are the byte code, *.pst are the source code • Parcels allows for fast atomic loading/unloading and prerequisite parcels • Good for dynamic loading and source code management

More Related