Similarities & differences between VSE and LSWVST

•  Similarities

•  Bytecode is compatible ( LSWVST has more bytecodes)
•  Primitive-Numbers are compatible ( LSWVST has more primitives )
•  VSE-Image can be loaded
•  VSE-SLL's can be loaded
•  MDI Support

•  Differences

•  continuously suppported enhanced - ported to other platforms & Processor architectures
•  written in pure Assembler Virtual-Machine size is about 112KB ( incl. X86 Jitter )
•  better JIT-Architecture ( no re-jitting required )
•  no Jit-size limittation
•  uses only Unicode-API in Virtual-Machine
•  runs on WinCE ( X86 )
•  not dependent on Microsoft MSVCRT.DLL
•  only one EXE / DLL ( no v.exe Stub as PE-Image Store required ) - dependentdon the appartment model
•  no further DLL's required
•  doesn't support 16 Bit
•  doesn't support OS/2
•  doesn't support Win95 / Win32s
•  doesn't support VSE obsolete Blockclosure mode
•  Object-Image can be stored in PE-Section of Virtual-Machine as a separate file or as resource.
•  SLL's are loaded from LSWVST start-Directory rather to be located from System-Path.
•  CompiledMethod's Bytecode can be stripped of and jitted-Code can be saved in Object-Image.
•  No Global-Functions in VM
•  No Differences in Runtime & Development-Time mode (  Primitive 77 returns false )
•  supports Multithreading
•  supports debugging of recursive callbacks
•  no limitation of Callback-Table size
•  supports multiple Object-Spaces with different Garbage-Collection
•  Float support for 40Bit and 80Bit
•  Can Host .NET CLR
•  Runs on Windows XP/ServicePack 2 and on Windows-Vista
•  Team environment based on Subversion