MCP-CMS: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 82: Line 82:
         </span>
         </span>
         </blockquote>
         </blockquote>
<blockquote style="position:relative;left:-5px;top:-10px;z-index:200;font-size:8px;">&dagger; This page and <a href="https://devops1.sameboat.network/About DCP">About DCP</a>
<blockquote style="position:relative;left:-5px;top:-10px;z-index:200;font-size:8px;">&dagger; This page and <a href="https://devops1.sameboat.network/About_DCP">About DCP</a>
  are top level specifying stories,  to the extent feasible, cog arch internals aren't divulged as I mean them to be adaptable without notice, everything else is source accessible by DevOps users.</blockquote>
  are top level specifying stories,  to the extent feasible, cog arch internals aren't divulged as I mean them to be adaptable without notice, everything else is source accessible by DevOps users.</blockquote>
<button title="show/hide the story details" type="button" class="collapsible"><div id="tldrDet">tl;dr</div></button>  
<button title="show/hide the story details" type="button" class="collapsible"><div id="tldrDet">tl;dr</div></button>  
Line 182: Line 182:
  'JCL' means things defined by an M-TRAN phrase grammar which can contain pure MINT blocks but general end use procedures are meant to be in Algol dialects. I dont mean it to be an acronym being both more general than job control and serving as the macro assembler of MCP. MCP thus maintains a distinction between what it and the host machine directly interpret.<br><br>
  'JCL' means things defined by an M-TRAN phrase grammar which can contain pure MINT blocks but general end use procedures are meant to be in Algol dialects. I dont mean it to be an acronym being both more general than job control and serving as the macro assembler of MCP. MCP thus maintains a distinction between what it and the host machine directly interpret.<br><br>
  A Smalltalk code set is part of the system concept and a "WFL workframe" is intended as an IDE and GUI for DCP/MCP (DGUI/SPO) but it is not required for ops and will not be  
  A Smalltalk code set is part of the system concept and a "WFL workframe" is intended as an IDE and GUI for DCP/MCP (DGUI/SPO) but it is not required for ops and will not be  
  available until I've worked it on the basis of the experience of the first working clusters. Separately, I will pick from the available FOSS visual programming pkgs to adapt for DCP/MCP, and
  available until I've worked it on the basis of the experience of the first working clusters. Separately, I will make a DCP/MCP adaptation based on the available FOSS visual programming pkgs,     and which I am calling DS G based on my experience with LabView/G, and which will be developed before WFL but with intent of later being a fa&ccedil;ade for it .
which I am calling DS G based on my experience with LabView/G, and which will be developed before but with intent of later being a fac&cedil;ade for WFL .
   </div>
   </div>
</blockquote><br><br>
</blockquote><br><br>