G@ Language and Compiler Software Technology.

G@ is a highly efficient programming language that I've been working on for a long time now. My work in developing the @on micro processor has put forward the requirement that I develop programming software for it and this in turn has driven me to examine general programming software logic.

The first thing I considered of course is the C++ software I'm using now. I acquired this software in 1997 and I admit I still don't know everything about it. Yes I write fully functional software with it yet their is some tricks I still don't know and the reason why is because the documentation is so huge and bewilderingly complex that I just haven't read it all. 

This brings up an advantage for G@. In G@ one person can master any imaginable programming job and get it done while this same job would take a team of programmers in another language. Productivity is the word and this will come from having the simplest and most reliable programming experience anywhere. How you might ask? It is called vision and genius.

Originally G@ had its start being very similar to C++ and was meant to be used on the @on processor. But better ideas influenced its evolution to the point that G@ is significantly different from any other programming language out there. I've even changed the visual appearance of windowed software by reengineering the view structure for software such as the multiple document interface. I do feel I have better ideas on such things as anybody else however doing this is a requirement because Microsoft Corporation has patents and copyrights on virtually every aspect of appearance and function of Windows software and they aggressively defend them.

Here are some key G@ points. First I removed the requirement for matching {}'s which can be a source of some very aggravating bugs and replaced it with a more fool proof formating system. I removed the ';' line terminator and replaced it with the requirement that all compile lines begin with '*'. This allowed me to restructure comment tokens since any line without a starting '*' won't be compiled thus it is a comment. The G@ universal document editor can supply '*' formatting in a smart way. Their are other format differences and I'll explain them at a later date.

More importantly however todays multi cored computers demand improved memory efficiency. I accomplished this by reengineering the software logic typical in the use of variables and function calls and virtual pointers. I've even reengineered thread logic for superior performance with the goal of having multiple cores concurrently executing within a single process. I've also reengineered memory heap logic and mass storage methods and their relationship to executables.

In G@ you have greater access to cpu registers and can even define them as variables all towards the superior performance advantage of G@. I have incorporated improved access visibility within a program and such is governed solely by syntax and not a scope restrictive wall. I'm currently improving the language structure in a way that will produce more logical constructs. Their will be functions, function objects and networks of objects that will make program logic logical and maximize execution performance.

@on, G@, @3S, @3i! and O3i! are the property of Mescitadel Think Tank and also claims O3S provided none can prove otherwise. What I mean is that the term O3S has been out their for some time but I know of none who actually have a functioning O3S.