A possibility to specify a mindcode or mlog text value will be added to the schematic definition:
schematic
name = "Base Builder"
tag = "Cardillan"
mindcode = """
#set program-name = "Base Builder";
#set program-version = "v0.4.0";
#set use-text-jump-tables = false;
"""
mlog = """
set ID 5
"""
These texts, if defined, will be automatically prepended to each mindcode/mlog value in processor configuration used within the schematics.
As shown, the primary use-case is to set compiler options for the entire schematics, but it could be used for other things as well. This adds support for compiler options without having to implement parsing them in the context of the Schemacode language, saving some work. As the error reporting can already handle code snippets, this reuses full compiler options handling already implemented in Mindcode.
When regions get implemented, it might be possible to redefine these values within the region, allowing local changes to the compiler options. We'll see.
A possibility to specify a
mindcodeormlogtext value will be added to the schematic definition:These texts, if defined, will be automatically prepended to each
mindcode/mlogvalue in processor configuration used within the schematics.As shown, the primary use-case is to set compiler options for the entire schematics, but it could be used for other things as well. This adds support for compiler options without having to implement parsing them in the context of the Schemacode language, saving some work. As the error reporting can already handle code snippets, this reuses full compiler options handling already implemented in Mindcode.
When regions get implemented, it might be possible to redefine these values within the region, allowing local changes to the compiler options. We'll see.