Imager::Expr - implements expression parsing and compilation for the expression evaluation engine used by Imager::transform2()


my $code = Imager::Expr->new({rpnexpr=>$someexpr}) or die ``Cannot compile $someexpr: '',Imager::Expr::error();


This module is used internally by the Imager::transform2() function. You shouldn't have much need to use it directly, but you may want to extend it.

To create a new Imager::Expr object, call:

 my %options;
 my $expr = Imager::Expr->new(\%options)
   or die Imager::Expr::error();

You will need to set an expression value and you may set any of the following:


A hashref defining extra constants for expression parsing. The names of the constants must be valid identifiers (/[^\W\d]\w*/) and the values must be valid numeric constants (that Perl recognizes in scalars).

Imager::Expr may define it's own constants (currently just pi.)


A reference to an array of variable names. These are allocated numeric registers starting from register zero.

By default you can define a 'rpnexpr' key (which emulates RPN) or 'expr' (an infix expression). It's also possible to write other expression parsers that will use other keys. Only one expression key should be defined.

Instance methods

The Imager::Expr::error() method is used to retrieve the error if the expression object cannot be created.


Imager::Expr provides only a few simple methods meant for external use:


Returns the compiled code.


Returns a reference to the array of numeric registers.


Returns a reference to the array of colour registers.


Returns a string with the generated VM ``machine code''.


Returns a string with the unassembled VM ``machine code''.

Creating a new parser

I'll write this one day.

Methods used by parsers:

@vars = $self->_variables()

A list (not a reference) of the input variables. This should be used to allocate as many registers as there are variable as input registers.


Set the return value of Imager::Expr::error()

@ops = $self->stack_to_reg(@stack_ops)

Converts marginally parsed RPN to register code.

Future compatibility

Try to avoid doing your own optimization beyond literal folding - if we add some sort of jump, the existing optimizer will need to be rewritten, and any optimization you perform may well be broken too (well, your code generation will probably be broken).