It's a library file containing the points of code, some of these files have starts at different points others are just use as controller libraries full of mini libraries.
So you have two unique functions of this programming language. 1 with libraries working off controller libraries in which all end functions are in assembly and have no dependencies else where in the library so you can include the points you want and not the ones you don't want you can even compile your own controller library from points of other controller libraries. 2 you can develop 2 or more similar programs working in the same library of points which means you can produce multiple apps each with a very similar standardised feel of the same kind.
you can tag each of the code points with the start point data otherwise all the code will be compiled and the selected start point used and what your not sure about and leave will be compiled unless tagged null.
Also the start points can be accompanies by inclusion of library for each start point and you can call the libraries for all as well with out having to repeat the call.
The naming scheme is very standardised to improve compile ability for example if you have all the variable's as a standard naming scheme that the compiler is aware of it can process better the variable and a data point number as opposed to working with a less standardised var name and programming scheme.
The name of the point function is of the naming scheme f1 F2 F3 f4 Not case sensitive directory names can be upto 12 letters long with no spaces and character limitation and you can put both directories and point functions in a directory . It's actually easier to remember a number and directory address than the current way of doing it although you can tag text to the function so if you leave the mouse over the function you'll get the text.
The naming scheme of variables V1a1 a type of integer V1a2 another integer of the same type V2a another type of integer, V1b1 a type of float V1c1 a type a character v1d1 a type of string v1e1 a type of array v1f1 a type of list.
Adding custom variable data types requires writing in an adequate data type compiler extension which is some more advanced coding.
If I said V1c1 = v1d1 I would have to use the config function <<(in here would go the settings)
you can tag the end of line ; to add notation and you can pile up these lines of code however you want to.
The code point address goes in the address bar.
you've got your standard operators and all standard functions of of the same name scheme as anything else only the primary function's are f1() f2() ect not dirname.dirname.f2() ect.
directory names are not case sensitive.
You can of course call a function up with out setting anything in the brackets.
This way of coding is simple and you can analyse a lot of code at once with out scrolling down as much plus less typing is involved
It can deal with c level data types but fall back better on assembly.
There's much room for optimisation but not a lot of room for thrills and bomph.
if you put V1c1=; not case sensitive then I would clear the variable loads of little tricks like that add up to a compact little niche programming environment.
For a variable to be global it can be defined at any point it's upto the programmer to get the issue right thus making it easier for the compiler with gv variables instead of v variables. This all helps with coping with redundancy and garbage collection if the programmer programs it properly.
To close the point you use :: at either the end or as part of decision this helps with garbage collection. It's like a kind of assembly based short hand.