Hi efgee,
Many thanks! I welcome your input.
Oxygen is still in its alpha phase but I hope to bring it to a point of stability in about four months time and produce a proper manual. At present, I am putting it through a series of fitness tests to see how it stands up as a language when exposed to a variety of APIs.
O2 refers to an earlier phase of development when Oxygem was an Assembler/Linker. O2H added the Basic language as a layer on top. The #basic or #o2h directives activate Basic functionality.
You will find a CHM manual for O2 in the thinBasic\help folder.
Compiled Oxygen files generally rely on thinBasic_Oxygen.dll to access the runtime library but there is a #Independent mode which allows the run time library to be compiled from source directly into the application, making it self-sufficient. I have used this mode to compile the first 64bit Executables (Very limited library at this stage).
I am documenting the Language reference in one of the source code files: currently o2keyw.bas. This contains all the primary keywords used by Oxygen (except for Asm instructions), with their internal codings and descriptive database which can be used to generate the manual automatically.
Doing it this way will keep the manual content synchronised, whatever the format - whether plain text, HTML or CHM.
Charles
Bookmarks