MCP-CMS: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
No edit summary
Line 178: Line 178:
   Procedural WFL is translated from source text to A60/C, then compiled and linked to the Barton machine, or directly interpreted by genie or MINT. Non-WFL blocks are compiled and bound  
   Procedural WFL is translated from source text to A60/C, then compiled and linked to the Barton machine, or directly interpreted by genie or MINT. Non-WFL blocks are compiled and bound  
  and used in the concrete context of the DS which they form as extensions of the WFL/B machine.<br><br>
  and used in the concrete context of the DS which they form as extensions of the WFL/B machine.<br><br>
  The JCL is defined by an M-TRAN phrase grammar which can contain pure MINT blocks but general procedures are meant to be in Algol dialects. Although I call it JCL, its not an acronym being both more general than job control and serving as a directly interpreted lang of MCP. <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 main vehicle of the directly interpreted lang of MCP. <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.
  available until I've worked it on the basis of the experience of the first working clusters.