As the resources seem to fall short of expectations, ---(---)--this statement should be deleted for the reason that a hardware technician expressed to me, was that "the laptop had a bad board, etc." , /--I bought that--/, and not as a result of updates that the people hype were expressing--- and falling back to the a less than double-G cpu - experience(with the busted screen), LISP continues its pre-ordained reference point of assessing the state of relevance of calling this ducksoop a thing. ... ... This "LISP ARRARY" seems able to hold the levels of trampolining around these abstractions before, after, and around while, the state of being at REST is contained at and in the same instance.
Until all of the parts names have a frame of reference for context, verbal abstractions seem like a way to hint at the spell's intentions ... there is a common thread in these semantical under-tones to try to keep the headers above VLSI details, and -at- the level of conversational intonations.
not sure if the array can be viewed as is but ...
the bottom appears to be an array dimension property ...closure on dimensions???
(( ((uu).(( ((pp.((ss(ll)).(ff(ww) ))).pinc).(ntz)).(xyz) )).(((bbbb.(aaaa(abcdabcd(abcdabcd)) )).000)
.(( ((001.(002.003)).(23D.(23E.23F) )) ))
)).001).(( ((002(003.004)).(23E.(23F.000) )) ))
)).002).(( ((003.(004.005)).(23F.(000.001) )) ))
)).23F).(( ((000.(001.002)).(23C.(23D.23E) )) ))
;;;THE STRUCTURE NEEDS TO BE CIRULAR::
the (LISP)declarations continue to express wanted discriminations like:: the wanted (rows)\column(fied)-vectors [displaced] on the (16)EXCEL(ed)- “pinc” data field with/by a width of the (16) 00Fhex-columns
;;;these key variables appear as another way to "order" a discriminate nature in the slot-ted declarations;;
((bbbb.(aaaa(abcdabcd(abcdabcd)) )) ::= actual addresses(@c control values)
;;;although there are many slots, this '(uu) needs to be the most special because this is the most atomic form;;;
( ((uu) ??? how to declare the “special-structure(color-discrimination) most conveniently and correctly???
these semantical disclosures or in want of the syntactic sugar LISP can deliver when words stretch into the realm of spells and potions ...
this sequence is just a representation of one line-output(8_LEDS), where the @c( control_addr) is not an-output, but nonetheless is represented in the structure to allow for the conditional cases when a LED is not connected to a LIGHT_PIPE ...
The LISP-array feels like a construct to use that slot-key-fields would allow displacement on the arrangement /* trying to find the magical-words to fit the controlling structures in the same place(location) as the data-structures */
TRUE in LISP ...and TRUE ... In the concept modeling profile, /// every property holder is equivalent to one topmost class (⊤) of which all other classes are subclasses. Thus, a property of a property holder is “inherited by” all subclasses and usable in any instances. /// ...
... the emperor has no CLOS ...
Whether a date gets added here is ... ///open before ... publishing ...plodding along/// continuing in this way towards the virtual reality in stating how places are circular in LISP sharp (#) semantics, we venture on suggesting the key slots will open the doors along the ROADM ... ... According to -https://en.wikipedia.org/wiki/Reconfigurable_optical_add-drop_multiplexer- ,,, This allows individual or multiple wavelengths carrying data channels to be added and/or dropped from a transport fiber without the need to convert the signals on all of the WDM channels to electronic signals and back again to optical signals. ... sounds like a complicated way to say, "change colors". Along this ROADM road is where I appear to want this structure's anatomy to unfold. But at the moment this structure's circular UML-protocol-state-machined/lispy nature can only be seen way down there in its VLSI (very -large-scaled-integration) format. What is desired is the ability to step back from this view to be able to see where these protocols can be used in NBI (north-bound-interfaces), API (application-interfaces) for the new-world's SDN (software-defined-network) architectures, while not becoming an astronaut myself.,.
Thought that the new inputs were added in a top-down fashion. But will start, adding inputs under dividers, in a bottom-down fashion for now. Seems the page will become long, but page shape isn't at the top of the list today. The DXF file isn't usable just yet. May piece together some simpler format that can display a LET/LED array here (in this page) which may show what the consequences of the spreadsheet/array structure has on the concept's ideals.
An actual LET display may be worrisome here. The structural consequences maybe'll request operational statistic variables.