Doing name lookups on the bus.

No doubt. at least I, will put the pcked char symbol table to the universal,, then snippets cn bind to it, ge their names mnaged anonymously.  What are the calls?

import name_segments;
GetDef key def;

That call takes key and locates its def, and on return the args list is modified to show that.  The call is one step, in the address space. Consistency snippet manages named segments, the symbol function can do names spaces, and partition the snippet callers.

Thus, we can give all the snippets full functionality of front end table with zero effort on theirpart, they set the key and call to that entry.  The import is the name space partition and ensures that key is partitioned in symbol table to match args partition, thus utilizing args completeness property.  If named segs are consistent, then data manager knows how to partition key names for important function, apriori, for uniqueness.

The expanded call does the trick also:

GetSeg namedseg key def; # 

note, GetSeg can be overloaded,

GetSeg illistrates an important concept, it is a nice name and we would like to re-use it. Consistency manager uses it, and so does symbol manager. The basic definition in, this can be overloaded, used by both, except when tightly bound, they will need alternative calls.

Here the partition is on named segs since the caller and called are tightly bound, like a function call, named seg is a consistent partition of key values..  So we go with one or more symbol tables, not necessarily one per snippet; expand the range here because it gives us the opportunity to build powerful symbol manager for enterprise control, snippet shared.