MCP-CMS: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 117: | Line 117: | ||
Upon successful connect, the launch link above results in an ODT session with this shell in the browser having supplied the default <b>cande</b> for the parameter 'mcpcms command' to the connect above. Aside from adaptations for the MCP machine model, it is just zsh however and the following alternates can be specified or run as a subshell with <b>cande <subshell></b>. You can also leave the field blank in which case you will be at the ODT level with bash. | Upon successful connect, the launch link above results in an ODT session with this shell in the browser having supplied the default <b>cande</b> for the parameter 'mcpcms command' to the connect above. Aside from adaptations for the MCP machine model, it is just zsh however and the following alternates can be specified or run as a subshell with <b>cande <subshell></b>. You can also leave the field blank in which case you will be at the ODT level with bash. | ||
<ul><li><b>shcl</b> </li><li><b>hsh</b></li><li><b>upsh</b></li></ul> | <ul><li><b>shcl</b> </li><li><b>hsh</b></li><li><b>upsh</b></li></ul> | ||
for lisp, haskell, and prolog respectively. MCP embeds sbcl, ghc, and swi prolog as libs and code in these shells can interact with those parts of DCP/MCP directly. In the BootKEE epoch, before DCP WFL is generally available, DCP is programmed as jobs via these shells . | for lisp, haskell, and prolog respectively. DCP/MCP embeds sbcl, ghc, and swi prolog as libs and code in these shells can interact with those parts of DCP/MCP directly. In the BootKEE epoch, before DCP WFL is generally available, DCP is programmed as jobs via these shells . | ||
<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. | ||
