How to install a new syntax engine

At the console, the statement:

python  // Adding syntax perfectly ok

Should work, when pipes are up or when Python is compiled as a shared.

The console loop puts itself in syntax mode, essentially allowing Python to control the command line, both input and output.  Python has access to all the symbol tables on the Bus, it can directly feed Xchars, for example, (all snippets generally use the fast symbol table).  Python has access to the Console Loop symbol table, So Python can set up command line macros. 

Python is on the Bus, all the snippets have universal interfaces, Python need only know a bit about the command sequence for any given snippet. Console loop designed this in, or more honestly, I kept all this in mind when doing the code. You will note that Default does all its language interpretation right on the command line, assembly code are executable linux commands for the Default snippet, is a good way to put it.  That means Python or Go, have access to the shunt system, can handle the cursor manager, run xchars, and can use Hardly stack codes when that is available. More importantly, we will get the join system up and running as a set of snippets, better approach than Tensor flow for AI.

The system has namespaces because the snippets use high speed packed char symbols, as good as call set up.  We can adapt our file expression syntax for reuse as a namespace selector.

All this stuff packs right in, mostly re-entrant, I dunno how many times ExecCommand makes recursive calls, 20 30 deep as it executes default assembly right off the args list.  This approach, I am convinced, will out do MS Power shell in a minute, and the packed char symbol table concept, universal interface will drive the snippet industry to long term growth.  I know, I am the snippet pro, there was never a code too short for me.  The entire approach is to get functions up, and running within the enterprise namespace almost right away, console loop even accepts code that crashes, just fine with console loop.

I have not even touched on the possibilities with multi-process access to a single, infinitely long args list, the idea that a code can walk the line of all corporate resources in linear fashion is fairly eye catching.

Nor is this idea far fetched from advanced shells being developed in the industry, and I look.  Good stuff out there, I steal ideas all the time.  My plea is simple, let us ripen the ideas a bit, talk about what all these shells might have in common.