Defining functions in Default

abc() {
some stuff
}

Cannot put anything into the parenthesis except an expression. The interpretor, onseeing this, will lay out the code, rghthere on the args list, right at the fist position and use as much as is needed to produce an expression and a mcro. Loks like:

abc size expr size [stuff] macro size [stuff]

It always produces h size element, counts the enclosed block and will nest I am sure. The bolded terms are commands on the linux bus;  macro and expr are public, meaning the console loop finds them.  abc is defined in the syntax. I am thinking that we get simple persistence by reading in a Default script file, and leaving it in the source buffer until further notice.  Very simple, works in Default, dn't need Hardly.  I have function definitions mostly working, and I am still under 800 lines and one file and no headers And hat gives you console loop, files and module loading.  Xchars is a separate package, all four hundred lines of that code. Power at your finger tips and a gcc default.c -ldl does it, I am still working on a configure file for that.

The world is a snippet

If you want something done, ask for it, there is a snippet on the Bus that will attempt it.  When you have high powered syntax engines backing you up, then all your system functions become snippets. Gcc becomes a bunch of loadable/ Sure, why not, give them all the universal syntax. The command module call call gcc, link, lib, or anything else, in whatever order, as long as all parties agree on the structure of args. Like have Shunt around for general purpose, all loaded and ready for ear.  Doing big compiles? Load up all the tool components, then work with your favorite syntax engines. Mix and match, as long as you can express your functions in the syntax chosen.