$PP => bool

Set default for "pp" compile argument. Takes precedence over environment "DATA_SAH_PP".

$CORE => bool

Set default for "core" compile argument. Takes precedence over environment "DATA_SAH_CORE".

$CORE_OR_PP => bool

Set default for "core_or_pp" compile argument. Takes precedence over environment "DATA_SAH_CORE_OR_PP".

$NO_MODULES => bool

Set default for "no_modules" compile argument. Takes precedence over environment "DATA_SAH_NO_MODULES".

new() => OBJ

Compilation data

This subclass adds the following compilation data ($cd).

Keys which contain compilation result:

$c->comment($cd, @args) => STR

Generate a comment. For example, in perl compiler:

 $c->comment($cd, "123"); # -> "# 123\n"

Will return an empty string if compile argument "comment" is set to false.

$c->compile(%args) => RESULT

Aside from arguments known by the base class (Data::Sah::Compiler::Prog), this class supports these arguments:

• pp

  Bool, default false. If set to true, will avoid the use of XS modules in the generated code and will opt instead to use pure-perl modules.

• core

  Bool, default false. If set to true, will avoid the use of non-core modules in the generated code and will opt instead to use core modules.

• core_or_pp

  Bool, default false. If set to true, will stick to using only core or PP modules in the generated code.

• whitelist_modules

  Array of str. When "pp"/"core"/"core_or_pp" option is set to true, the use of non-appropriate modules will cause failure. However, you can pass a list of modules that are allowed nevertheless.

$c->add_runtime_use($cd, $module [, \@import_terms ])

This is like add_runtime_module(), but indicate that $module needs to be "use"-d in the generated code (for example, Perl pragmas). Normally if add_runtime_module() is used, the generated code will use "require".

If you use "$c->add_runtime_use($cd, 'foo')", this code will be generated:

 use foo;

If you use "$c->add_runtime_use($cd, 'foo', ["'a'", "'b'", "123"])", this code will be generated:

 use foo ('a', 'b', 123);

If you use "$c->add_runtime_use($cd, 'foo', [])", this code will be generated:

 use foo ();

The generated statement will be added at the top (top-level lexical scope) and duplicates are ignored. To generate multiple and lexically-scoped "use" and "no" statements, e.g. like below, currently you can generate them manually:

 if (blah) {
     no warnings;
     ...
 }

$c->add_runtime_no($cd, $module [, \@import_terms ])

This is the counterpart of add_runtime_use(), to generate "no foo" statement.

See also: add_runtime_use().

$c->add_sun_module($cd)

Add Scalar::Util::Numeric module, or Scalar::Util::Numeric::PP when "pp" compile argument is true.

DATA_SAH_PP => bool

Set default for "pp" compile argument.

DATA_SAH_CORE => bool

Set default for "core" compile argument.

DATA_SAH_CORE_OR_PP => bool

Set default for "core_or_pp" compile argument.

DATA_SAH_NO_MODULES => bool

Set default for "no_modules" compile argument.