The main focus was Ruby integration into NHI10 and the new object-database in the backend.
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