23 #if defined (HAVE_CONFIG_H) 173 tree_binary_expression *
196 ct = simplify_and_or_op (ca, cb,
t);
static octave_value::compound_binary_op simplify_mul_op(octave::tree_expression_ptr_t &a, octave::tree_expression_ptr_t &b)
octave_value::unary_op op_type(void) const
OCTAVE_EXPORT octave_value_list return the number of command line arguments passed to Octave If called with the optional argument the function t
tree_expression * tree_expression_ptr_t
nd example oindent opens the file binary numeric values will be read assuming they are stored in IEEE format with the least significant bit and then converted to the native representation Opening a file that is already open simply opens it again and returns a separate file id It is not an error to open a file several though writing to the same file through several different file ids may produce unexpected results The possible values of text mode reading and writing automatically converts linefeeds to the appropriate line end character for the you may append a you must also open the file in binary mode The parameter conversions are currently only supported for and permissions will be set to and then everything is written in a single operation This is very efficient and improves performance c
static octave_value::unary_op strip_trans_herm(octave::tree_expression_ptr_t &exp)
calling an anonymous function involves an overhead quite comparable to the overhead of an m file function Passing a handle to a built in function is because the interpreter is not involved in the internal loop For a
tree_binary_expression * maybe_compound_binary_expression(tree_expression *a, tree_expression *b, int l, int c, octave_value::binary_op t)
virtual bool is_unary_expression(void) const
tree_expression * operand(void)
static octave_value::compound_binary_op simplify_ldiv_op(octave::tree_expression_ptr_t &a, octave::tree_expression_ptr_t &)