Text::...nctions(3pm)

πŸ“¦
version 2.23 Β· 3 versions
, in debian trixie, ubuntu noble, ubuntu resolute, ubuntu stonking

πŸ’– Text::MicroMason::Functions πŸ’–

okay bestie, so this is the function exporter for Simple Mason Templates β€” it's a page from the User Contributed Perl Documentation, and it's genuinely so useful. sit down, hydrate, let's go 🫢


✨ SYNOPSIS ✨

Use the execute function to parse and evaluate a template:

use Text::MicroMason::Functions qw( execute );
print execute($template, 'name'=>'Dave');

Or compile it into a subroutine, and evaluate repeatedly:

use Text::MicroMason::Functions qw( compile );
$coderef = compile($template);
print $coderef->('name'=>'Dave');
print $coderef->('name'=>'Bob');

Templates stored in files can be run directly or included in others:

use Text::MicroMason::Functions qw( execute_file );
print execute_file( "./greeting.msn", 'name'=>'Charles');

Safe usage restricts templates from accessing your files or data:

use Text::MicroMason::Functions qw( safe_execute );
print safe_execute( $template, 'name'=>'Bob');

All above functions are available in an error-catching try_* form:

use Text::MicroMason::Functions qw( try_execute );
($result, $error) = try_execute( $template, 'name'=>'Alice');

🌸 DESCRIPTION 🌸

So, alternative to the object-oriented interface? Yes ma'am. Text containing MicroMason markup code can be compiled and executed by calling the following functions. it's giving one-line wonder ✨

okay but real talk, important caveat incoming:

Please note that this interface is maintained primarily for backward compatibility with version 1 of Text::MicroMason, and it does not provide access to some of the newer features.

Every single one of these functions creates a brand new MicroMason object β€” including any necessary traits like Safe compilation or CatchErrors for exceptions β€” and then passes its arguments to an appropriate method on that object. one function, one fresh object, no cap πŸ’…

You may import any of these functions by including their names in your use Text::MicroMason statement.


πŸ¦‹ Basic Invocation

To evaluate a Mason-like template, pass it to execute():

$result = execute( $mason_text );

Alternately, you can call compile() to generate a subroutine for your template, and then run the subroutine:

$result = compile( $mason_text )->();

If you will be interpreting the same template repeatedly, you can save the compiled version for faster execution:

$sub_ref = compile( $mason_text );
$result = $sub_ref->();
(Note that the $sub_ref->() syntax is unavailable in older versions of Perl; use the equivalent &$sub_ref() syntax instead.)

πŸŽ€ Argument Passing

You can also pass a list of key-value pairs as arguments to execute, or to the compiled subroutine:

$result = execute( $mason_text, %args );

$result = $sub_ref->( %args );

Within the scope of your template, any arguments that were provided will be accessible in the global @_, the %ARGS hash, and any variables named in an %args block. three ways to catch the same vibe 😌

For example, the below calls will all return '<b>Foo</b>':

execute('<b><% shift(@_) %></b>', 'Foo');
execute('<b><% $ARGS{label} %></b>', label=>'Foo');
execute('<%args>$label</%args><b><% $label %></b>', label=>'Foo');

🧚 Template Files

A parallel set of functions exist to handle templates which are stored in a file:

$template = compile_file( './report_tmpl.msn' );
$result = $template->( %args );

$result = execute_file( './report_tmpl.msn', %args );

Template documents are just plain text files that contains the string to be parsed. The files may have any name you wish, and the .msn extension shown above is not required. name it whatever, it's your world πŸ’–


😭 Error Checking

Both compilation and run-time errors in your template are handled as fatal exceptions. The provided try_execute() and try_compile() functions use a mixin class which wraps an eval { } block around the basic execute() or compile() methods.

In a scalar context they return the result of the call, or undef if it failed; in a list context they return the results of the call (undef if it failed) followed by the error message (undef if it succeeded). for example:

($result, $error) = try_execute( $mason_text );
if ( ! $error ) {
  print $result;
} else {
  print "Unable to execute template: $error";
}

A matching pair of try_*_file() wrappers are available to catch run-time errors in reading a file or parsing its contents:

($template, $error) = try_compile_file( './report_tmpl.msn' );

($result, $error) = try_execute_file( './report_tmpl.msn', %args );

For more information, see Text::MicroMason::CatchErrors.


πŸ”₯ Safe Compartments

If you wish to restrict the operations that a template can perform, use the safe_compile() and safe_execute() functions, or their try_*() wrappers. protecting your files and your data? iconic behaviour, honestly πŸ‘‘

For more information, see Text::MicroMason::Safe.


🌈 SEE ALSO 🌈

  • For an overview of this templating framework, see Text::MicroMason.
  • For distribution, installation, support, copyright and license information, see Text::MicroMason::Docs::ReadMe.

and that's the whole page bestie!! πŸŽ€ this lil doc is from perl v5.36.0, dated 2023-08-10, and honestly? she ate. go forth and template responsibly πŸ’…βœ¨πŸ¦‹

πŸ“¦ where this page comes from