MCP-CMS: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 174: | Line 174: | ||
</table><br>¹<font size=1>An APP is a JOB with device/station dependencies</font> ²<font size=1>headless squeak, using my cog build for Sista and multi-threading.</font><br> | </table><br>¹<font size=1>An APP is a JOB with device/station dependencies</font> ²<font size=1>headless squeak, using my cog build for Sista and multi-threading.</font><br> | ||
</center> | </center> | ||
Intrinsic means the lang is native to MCP/WFL and doesn't require COMPILE or BIND to produce a RUN eligible object title. SPO/DGUI elements are | Intrinsic means the lang is native to MCP/WFL and doesn't require COMPILE or BIND to produce a RUN eligible object title. SPO/DGUI elements are intrinsic to DCP but are isolated to st images and run | ||
ordinary MCP mix elements. Enterpise facing means oriented to programming users of the system, Machine facing means me, for my motivation, satisfaction and design intent of real machine | as ordinary MCP mix elements. Enterpise facing means oriented to programming users of the system, Machine facing means me, for my motivation, satisfaction and design intent of real machine | ||
of the core super-OS. | independence of the core super-OS as much as the nominal sense. | ||
Users can create their own semantic spaces by using WFL and the standard modern high level lang blocks while the MINT and Algol elements are my private programming of DCP/MCP not meant | Users can create their own semantic spaces by using WFL and the standard modern high level lang blocks while the MINT and Algol elements are my private programming of DCP/MCP not meant | ||
for user consuption but visible to satisfy transparency requirements. | for user consuption but visible to satisfy transparency requirements. | ||
