| Appx compiles process specifications into a form that minimizes runtime processing. It's a bit difficult to describe the format. The Appx engine is similar to a Java VM (virtual machine) or the .NET environment. When we designed Appx, we defined an ideal execution environment that doesn't actually exist in any hardware - we implemented the execution environment in software. There are a number of different execution components. ILF code is executed in an optimized register-based software CPU (there are about 500 op-codes in the instruction set - the opcodes do things like "convert from binary form to packed-decimal", "jump to label", "invoke a subroutine"). Process specifications are interpreted by the process interpreter - when we build an EM, we resolve as many details as possible - the basic theory being "do it once, at compile time" rather than "do it every time you run this process". That's one reason that it would be difficult to add indirection as some people have asked for - indirection means that you defer as many decision as possible until runtime.
So we don't really generate code in the way that some tools do. We don't generate C code that then gets compiled into a program. Appx is a compiler, interpreter, and VM all rolled into a single package.
|
FAQ's - APPX Software, Inc. : 
How to turn off full selection (highlighted) of text fields in change mode.