MCP-CMS: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 121: | Line 121: | ||
Upon successful connect, the launch link above results in an ODT session with this shell in the browser having supplied a parameter to the connect to invoke <b>cande</b>. | Upon successful connect, the launch link above results in an ODT session with this shell in the browser having supplied a parameter to the connect to invoke <b>cande</b>. | ||
Aside from adaptations for the MCP machine model, it is just zsh however and the following alternates are available to establish different shell behaviours in support of the KEE: | Aside from adaptations for the MCP machine model, it is just zsh however and the following alternates are available to establish different shell behaviours in support of the KEE: | ||
<ul><li><b>shcl</b> </li><li><b>CANDE HSH</b></li><li><b>upsh</b></li></ul> | <ul><li><b>CANDE shcl</b> </li><li><b>CANDE HSH</b></li><li><b>CANDE upsh</b></li></ul> | ||
which have the lisp, haskell, and prolog natures, respectively. | which have the lisp, haskell, and prolog natures, respectively. Where the CANDE prefix indicates these modified to run as commands in cande/zsh in a MCP context. While in general Lisp and Prolog implementations can vary in the Boot KEE, these lang shells are integral with | ||
DCP which uses sbcl and swipl, respectively. In the Boot KEE epoch, before DCP WFL is available DCP is implemented in these shells over its machine model. | DCP which uses sbcl and swipl, respectively. In the Boot KEE epoch, before DCP WFL is available DCP is implemented in these shells over its machine model. | ||
<b>mcpcms</b> can be accessed from various connect points such as the launch link above in an AKPERSONs session. | <b>mcpcms</b> can be accessed from various connect points such as the launch link above in an AKPERSONs session. | ||
