#DOCUMENTATION by cg
authorClaus Gittinger <cg@exept.de>
Thu, 03 Nov 2016 15:28:59 +0100
changeset 4033 2856dce456a8
parent 4032 58a37f863591
child 4034 0a8789ead3b6
#DOCUMENTATION by cg class: stx_libcomp comment/format in: #documentation
stx_libcomp.st
--- a/stx_libcomp.st	Thu Nov 03 15:01:17 2016 +0100
+++ b/stx_libcomp.st	Thu Nov 03 15:28:59 2016 +0100
@@ -43,12 +43,19 @@
     This library contains the Smalltalk parser and bytecode compiler,
     and related support classes (AST representation).
 
-    This compiler is used when code is changed within the running IDE or application.
-    It generates bytecode methods, which are further translated to machine code by the VM,
-    when first executed. 
-    This is not to be confused with the stc-compiler, which generates plain machine code, which
-    is packaged in compiled class libraries. Usually, end user applications are deployed as 
-    stc-compiled binary code. And only patches or dynamically generated code uses bytecode methods.
+    This compiler is used when code is changed within the running IDE or application,
+    and when source code is loaded.
+    It generates bytecode methods, which are (typically) further translated to machine code by the VM,
+    when first executed 
+    (although for some architectures, no JITTER is available, and the bytecode will be interpreted, 
+     which is of course much slower).
+     
+    This is not to be confused with the stc-compiler, which generates plain machine code, 
+    which is packaged into compiled class libraries and runs with very good performance. 
+    Usually, end user applications are deployed as stc-compiled binary code. 
+    And only patches or dynamically generated code uses bytecode methods.
+    Therefore, the speed of the bytecode interpreter is usually not at all relevant to a deployed app's 
+    overall speed (and also not to the ST/X IDE itself, as it also consists of precompiled machine code).
 "
 ! !