ChasmCodeSupplemental

So you may be asking yourself... what is a supplemental code file? It is a file where you can place your implementation code separated from the .h and .C files. It is another degree of abstraction. Why is this useful? Well, personally, it enables me to create .h and .C files which are throwaways. As the spec changes, you can just regenerate these files. For most people, this is not needed. For me, it is needed for testing.

NOTE: Supplemental files are not parsed by chasmprocess so therefore if you use CHASMCONCEPT in the supplemental file, it will cause an error because it will be sent to the compiler as CHASMCONCEPT without resolving into its actual type.

To Create a Supplemental code file:

• When running the chasm2C command, add the -s parameter to chasm2C. This will then generate a concept_sup.h file as well as adding extra code to the concept.[Ch] files that enables the code in the concept_sup.h file to be spliced in.
• If the compiler is having trouble finding the supplemental header, make sure you specify it as a local or global header by throwing in the -l option for global headers or the -L option for local headers. (global is the default)

Here is an example Supplemental Header.