The ini parser will come in handy for configurations, for example once
the time has come for adding shader packs.
The parser isn't tested yet; writing some (automatic) tests would be a
really good idea.
The utilities are grouped into the following categories:
- Math
Matrices, vectors and special rounding functions are included in the
math category. This still is severely lacking in functionality.
- Containers
Datatypes for storing arbitrary data in a special way, for example
for being able to search through it quickly, in the case of a map.
Currently the only function in this category is for testing how long
a string is, with a maximum number of bytes to check.
- Allocation
Special-purpose memory allocators with restrictions on what they can
allocate. The restrictions are used to be faster in those use cases.
- UUID
Universally-unique identifiers are used to identify one specific
object within the engine's lifetime.
The key for getting the path of the own module in the includes.txt is
no longer '{self}', but rather '{module}', as that is a little easier
to understand.
The include statements generated from the 'includes.txt' have'nt been
correct because of a prefixed string 'modules/' infront of the project
path. The local includes were also not working because the 'modules/'
path element was missing between the project path and the module name.
The build-script assumed that it was nested two levels deep from the
project's root directory, even if it is only nested one level deep;
that bug is now fixed.
Eric-Paul Ickhorn