Name

ConfigParseComments — (obsolete) treat config meta-directives as plain comments

SYNOPSIS

Yes | No

DESCRIPTION

When disabled (set to No), configuration meta-directives such as #include, #ifdef and #ifndef, are treated as pure comments with no specific meaning.

However, since those were originally borrowed from the C preprocessor, and, true to their C heritage, they started with an '#' (hash) character in Interchange versions up to and including 4.6.

This was inconvenient for newcomers who were easily misguided by thinking those were just comments, so Interchange versions 4.7 and up were changed to use the meta-directives without the hash prefix.

DIRECTIVE TYPE AND DEFAULT VALUE

Global directive,
Catalog directive

EXAMPLES

Example: Config parser behavior with ConfigParseComments disabled

ConfigParseComments No

#include comment
# This, and the above line, are pure comments.

# You better prepare the file named 'comment' for the following one:
include comment

NOTES

This directive is obsolete as of Interchange 5.5.0, and the behavior is as if ConfigParseComments No was specified.

AVAILABILITY

ConfigParseComments is available in Interchange versions:

4.6.0-5.7.0 (git-head)

SOURCE

Interchange 5.7.0:

Source: lib/Vend/Config.pm
Line 463

['ConfigParseComments',     'warn',     ''],

Source: lib/Vend/Config.pm
Line 584

['ConfigParseComments',     'warn',     ''],

Source: lib/Vend/Config.pm
Line 2987 (context shows lines 2987-2999)

sub parse_warn {
my($name, $val) = @_;

return '' unless $val;

::logGlobal({level => 'info'},
      errmsg("Directive %s no longer supported at line %s of %s.",
          $name,
          $.,
          $configfile,
      )
);
}

AUTHORS

SEE ALSO

DocBook! Interchange!