The parser directives are syntactic constructions very similar to the C/C++ preprocessor directives (although the IDL parser in the Massiv doesn't have any preprocessor). Each directive begins with the # character and cannot be split into more lines (the only exception is a nasty C++ compatible hack - enclosing the end of line into a multiline comment). List of all supported directives follows:
#error STRING
Prints STRING to the stderr and causes the processor quit with an error.
#warn STRING
Prints STRING to the stderr.
#include STRING
The IDL processor will attempt to find a file specified by STRING in all directories contained withing the list of paths that should be searched. If the file is not found, the processor will stop with an error. Otherwise the parsing will continue and the contents of the relevant file will be put in place of the #include directive.
#import STRING
This directive has almost the same meaning as the #include directive. The difference is that nothing will be done if the file has already been imported or is just being processed. Importing should almost always be used instead of including to prevent duplicate symbol definitions.