|
Once such a system is implemented in a programming environment, such a discipline pays. Therefore, in order to place the same form on different vertexes, one has to produce a number of isomorphic copies, i.e., synonymous forms (in the above sense) with the same spaces. Or else, we may enrich the form names in order to be able to define as much forms as needed via rich name spaces. In practice, we do however often refer to “copies of a given form” without specifying these naming accents. Remark 4 In practice, lists are very useful. There is no list type in our setup, but one may easily mimick it as follows. We are working in the presheaf topos A more elegant way without using an indetermined number of cofactors for our list form works as follows: Consider the form ![]() and where . Here we denote the vertex forms for limits and colimits if we deal with discrete diagram schemes. The form is made for terminating the list entries and writing down the list’s length. This however is not a complete definition since we do not know whether such a form exists! This definition is circular, and the existence of the corresponding presheaves must be proven. This is in fact true, see (Mazzola, 2002, G.2.2.1), but the proof uses more than finite completeness. Despite the missing list type, the given types can be used to define more general list forms in the sense that general index sets can be used. To this end, let
, being the identity on the frame space . Observe that for any address module , we have since is final in . We then define the auxiliary form and finally set ![]() |