Namespace in the console loop

If I had to pick an honest standard, the using command should be implemented. In default it has a simple function. Within the enclosing block,look in this entry point first, and burp a syntax_error if not found. Very simple, when done InDeault:

Default {
using qt_chars;    # you are dumping my version for a better

Do any valid linux commands not otherwise involved in a Default expression or macro call. These all pass through, the Exec Command funcion recognizes the using parameter and does the urping and executing.

someexit();
} # close using command

Do it straight from command line:

using qt_chars # big mistake, my version has a future
NewConn conn
NwWin conn win 
... etc

It is easy to do, the two conflicting snippets can overload method names.  Each using command causes console loop to set up and bind a new symbol, like a macro, unless, in default, the using name is the same as the snippet file name. Data manager is setting up intelligent message routing through by programming the snippets and console loops as routers, and message packagers.

The console loop can manage name space nesting, it just takes the loop back through, somehow.

Using is an enterprise wide function, all the console loops know it, and so all the syntax engines will follow.  Using reports; all your mid level managers do this at report time, all the snippets get aligned, all the command routes established inside console loop, the proper consistency net established for data sharing,sql table names properly identified. The enerprise literally programmed for thursday afternoon report time.