|> Home > Documentation > Latest documentation > Global config directives > ConfigParseComments|
Specify whether to treat "#" as a comment when combined with C-preprocessor-style directives.
This is a Yes or No directive. The default is Yes.
This directive is only available for use in the global (interchange.cfg) configuration file, and will affect all websites running under the Interchange installation. It will not work in a website's local (catalog.cfg) configuration file.
Set to No if you want old-style "#include", "#ifdef" and "#ifndef to be treated as directives, rather than as comments. The default is Yes, which means both "#include" and "include" are treated the same. Use a space after the "#" if you really want to comment out the directive.
Prior to version 4.7, Interchange used a different syntax for the "include", "ifdef" and "ifndef" meta-directives in configuration files. The commands were borrowed from the C preprocessor and, true to their "C" heritage, they started with a "#" character.
Interchange configuration files, unlike "C", uses '#' to begin one-line comments. This meant that a newcomer at first glance might assume that the following two lines are both comments, whereas the second line was intended to be a live "#include" directive:
To begin to make things more consistent, Interchange 4.7 through 5.4 recognised those meta-directives without the leading '#', and the included Standard demo sets this directive to No so that lines beginning with "#" really were skipped as comments, regardless of what else was on the same line.