MCP-CMS: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
No edit summary
Line 124: Line 124:
     Aside from adaptations for the MCP machine model, it is just zsh however and the following alternates derived from existing pkgs to support the KEE:
     Aside from adaptations for the MCP machine model, it is just zsh however and the following alternates derived from existing pkgs to support the KEE:
     <ul><li><b>CANDE shcl</b> </li><li><b>CANDE HSH</b></li><li><b>CANDE 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 work with CL, HS, and LL MCP blocks, respectively. Here the CANDE prefix indicates the received pkgs are modified to run as commands from the CANDE/zsh MCS. While in general Lisp and Prolog implementations can vary in the BootKEE, these lang shells are intrinsic in DCP. In the BootKEE epoch, before DCP WFL is generally available DCP is programmed as jobs via these shells .
     which work with CL, HS, and PL MCP blocks, respectively. Here the CANDE prefix indicates the received pkgs are modified to run as commands from the CANDE/zsh MCS. While in general Lisp and Prolog implementations can vary in the BootKEE, these lang shells are intrinsic in DCP. 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.