the Forté Application Environment (Forté from now on) relies on a “layer” to equalise the differences amongst platforms: ftexec (+ libraries)
this is the Forté virtual machine that runs anything (compiled or interpreted) developed with the Forté IDE.
compiled vs. interpreted
interpreted: ftexec takes a .btd file as input
compiled: the produced executable is linked with ftexec.o
the way Forté manages to mix interpreted & compiled code is utterly clever, in the IDE most of the plans are 3GL objects made available to 4GL code, but some of the plans (AppModel, HTTPSupp, IIOP, LDAP, OLE, XMLSvr & XSLT) are 4GL TOOL interpreted projects.
the IDE itself is an interpreted bit of code (that has some interesting implications ... later) that can be ran with the following command :
ftexec -fi bt:$FORTE_ROOT/userapp/forte/cl0/forte -fr myRep -fw myWKS -fns myEnvNode:port
btree & other code containers
source code lives in text files so it's easy to version and archive. but Forté has its own version control & concurrency access mechanism and it all resides in the .btd & .btx
note for later: interpreted installed applications and development repositories both reside in a .btd file. btree not always the norm up to 3.0.G there used to be ctree & objectivity repositories, there are also clues that Forté Software Inc may have tried to fit the repositories into some SQLRepositories
No comments:
Post a Comment