theCompiler

UPDATE	changes since 26 sep 1924 : 133 files changed, 8358 insertions, 6071 deletions

SUMMARY	theCompiler - A tool to parse and understand header files (API) and then generate new code in a desired target language.
NEWS FROM: 30 oct, 2024	The main focus was Ruby integration into NHI10 and the new object-database in the backend. NEW features The alc compiler consists of three layers: frontend, middleware and backend. Up to now, a table-structure was used for the data in the frontend and backend, which worked well but showed some weaknesses over time, which led to the backend being converted to an object-structure. Both types of structure have their advantages and disadvantages. The table-structure is better suited for cross-object analysis and the object-structure is better suited for object-specific analysis. Unfortunately, only one type of data structure can be used at a time and so I decided to leave the frontend with the table-structure but convert the backend to the new object-structure. In order to support the new object-structure, the format of the meta-code-library-definition-file (META-FILE) was changed for the first time. Previously, the linking of the data from the various tables was done in the backend, but with the new object-structure this no longer makes sense and has been moved to the middleware. This in turn means that the attribute-database also needs the attribute-class, which then ensures that attributes can be assigned to the appropriate class at a very early stage. See also alc compiler

DETAILS	The main goal of theCompiler is to support Meta-Programming. At the beginning theCompiler started with C# and the lack of support for automatic api generation combined with a very "fault-tolerant" integration that ultimately ended in a runtime error. After the piece-by-piece conversion of LibMsgque into an object-oriented environment and the associated standardization of the language connection, theCompiler became more and more important and thus became a "swiss knife" of programming. The central tool to create source-code is BuildNhi1, which, after a few tests, calls the makefile where the compilation process is ultimately controlled. To avoid unnecessary translation work, theCompiler was programmed in such a way that just ONE run is enough to update all project files. The programmer writes HIS code independently of BuildNhi1 and ultimately carries out the final translation into the executable. If the API or an attribute was changed, then of course the BuildNhi1 must be called again in order to transfer this change to the entire project.
DEPENDENCIES	theCompiler was written in TCL.

Introduction

target	#1	#2	#3	#4	#5
theCompiler	alc compiler	alc goals	alc new C	alc parser	alc native

Files

README , INSTALL , NEWS, CHANGES