A_STATE_BLOG2

---

I am attempting to install Visual Studio to use the UML design which (with required included packages) is supposed to deliver C++ code ,etc, C#, from the UML diagrams... I have also a post about how to "get" xmi files installed into a VS model ... this is on hold ...

I want[ed] to try this route until I can acquire a "full license" for the MagicDraw file "protocol_state_machine" stored as an xmi file ...

I may have seen some mention of VS's (or maybe it was QutaumLeap's) ability to ... have a "method" of a state in a super-state, accessible to sub-states (actionable-objects), ... things seem to approach my LISP concept of the method being a non-classed object ...

The MagicDraw was the most revealing UML used that showed that the UML models could in some cases distill code in a C++ fashion for viewing by any interested onlookers.The saved MagicDraw-xml file was an attempt at trying to view what the application had saved as it's representation of the UML models without using the actual application's implementation models ... somewhere in this site the user's pages were supposed to be uploaded so references to them would be easy to display and discuss … this is conceptual ...

so here is another SPREADSHEET representation of the data's wished for table structure ...

… as to the urgency of having this picture's posting, let it be understood that certain column values are missing intentionally not purposely ... ... ,,, because during the life cycle of the cell-ular contents' certain pointer values were not re-constituted according to prescribed tables lookup functions.

LISP's ODBC, CLOS, CLIM, and other such manifastsations continue their revelations to the magicians that such is possible from the bottom up functionings ...