#include <Op_bones.hpp>

Inheritance diagram for Op< T1, op_type >:

Public Types
typedef T1::elem_type	elem_type
typedef get_pod_type < elem_type >::result	pod_type
Public Member Functions
	Op (const T1 &in_m)
	Op (const T1 &in_m, const elem_type in_aux)
	Op (const T1 &in_m, const elem_type in_aux, const uword in_aux_uword_a, const uword in_aux_uword_b)
	Op (const T1 &in_m, const uword in_aux_uword_a, const uword in_aux_uword_b)
	Op (const T1 &in_m, const uword in_aux_uword_a, const uword in_aux_uword_b, const uword in_aux_uword_c, const char junk)
	~Op ()
Public Attributes
arma_aligned elem_type	aux
	storage of auxiliary data, user defined format
arma_aligned uword	aux_uword_a
	storage of auxiliary data, uword format
arma_aligned uword	aux_uword_b
	storage of auxiliary data, uword format
arma_aligned uword	aux_uword_c
	storage of auxiliary data, uword format
arma_aligned const T1 &	m
	storage of reference to the operand (eg. a matrix)

Detailed Description

template<typename T1, typename op_type>
class Op< T1, op_type >

Class for storing data required for delayed unary operations, such as the operand (e.g. the matrix to which the operation is to be applied) and the unary operator (e.g. inverse). The operand is stored as a reference (which can be optimised away), while the operator is "stored" through the template definition (op_type). The operands can be 'Mat', 'Row', 'Col', 'Op', and 'Glue'. Note that as 'Glue' can be one of the operands, more than one matrix can be stored.

For example, we could have: Op< Glue< Mat, Mat, glue_times >, op_htrans >

Definition at line 30 of file Op_bones.hpp.