Nesting syntax engines

Everything on the Bus nests properly, unfolds and folds leaving args list intact.  Each syntax engines maintain the top of args list pointer, at any given nesting level, that pointer is going to represent free space.  Syntax engines are expected to build complex linux command sequences on the Bus.  Default, for example, is likely to be initialized with a ton of Bash scrips, which it blindly emits as required by, yet another syntax engine, python, and bash will be executing other snippets, on the Bus, they will have their own syntaxes. Two things make this work, argc is exposed and its state restored in the Turring complete system, and second, console loop will burp and bring everyone back to top level on an error.

Hence my desire to keep Default almost featureless.  As long as it is a tiny cog in the wheels of syntax engine, it survives.  It is really console loop that sells the concept, that and xchars. Console loop will know how to thread snippets, how to pipe transparently into any linux based utility, it keeps a robust symbol table, accessible by and other script, it knows what a loadable is, and knows how to hut down a consumer of some linux command. And it manages the linux command alignment, on the bus.  Console loop is really a DMA controller. Imagine a system composed of an array of Rasberry boards, running linux, all on a high speed DMA bus.    Console loop would be a simple processor card, even tinier and cheaper than a Rasberry, and it would keep the bus organized, commands on the bus aligned, and coordinate access to the bus via its command entry point list.

I fully expect to see that hardware built, it is a natural as we move AI to massive semantic network, and it already exists in proprietary form. The concept is a natural for open source multi-processing.

The system can be any shell

Any of the 5-7 popular shell systems can easily take over the bus as the user desires, console loop is so thin, and flexible, that users will not notice. The system built around arg list, not Default, not join. Args list was designed to take that concept well into hardware for command and control, deliberately removing impediments and moving the complexity up, allowing high speed methods on the bus.