The procedures andmap and ormap determine whether a predicate p returns true, false, or FAIL for all or some operands of an expression expr.

If expr is atomic, both andmap(p, expr, ...) and ormap(p, expr, ...) are equivalent to p(expr, ... ).

In general, andmap(p, expr, ...) returns true if p(opnd, ...) is true for all operands opnd of expr, returns false if any call to p returns false, and returns FAIL when calls to p lead to at least one FAIL result and any number of other true and FAIL results.

Similarly, ormap(p, expr, ...) returns false if p(opnd, ...) is false for all operands opnd of expr, true when any call to p returns true, and FAIL when calls to p lead to at least one FAIL result and any number of other false and FAIL results.

Both andmap and ormap have short-circuit ("McCarthy") semantics, which means that an answer is returned as soon as it can be determined. The predicate only evaluates at the operands of the expression expr until the result can be determined. The order in which the operands are examined is not specified. You should not rely on side effects of the predicate p.

For a table or array, p is applied to each entry of the table or array.

Since strings are atomic expressions in Maple, you cannot map a procedure over a string by using andmap and ormap. However, the StringTools package contains the exports AndMap and OrMap that provide this functionality.

The andmap and ormap commands are thread safe as of Maple 15, provided that evaluating the expression p is thread safe.

For more information on thread safety, see index/threadsafe.

andmap( type, [ 1, 2, 3, 4, 5 ], 'integer' );

$\mathrm{true}$

ormap( type, [ 1, 2, 3, 4, 5 ], 'integer' );

$\mathrm{true}$

andmap( type, [ 1, 2, 3, 4, 5 ], 'even' );

$\mathrm{false}$

ormap( type, [ 1, 2, 3, 4, 5 ], 'even' );

$\mathrm{true}$

andmap( isprime, [ 2, 3, 5, 7 ] );

$\mathrm{true}$

andmap( isprime, [ 2, 3, 5, 8 ] );

$\mathrm{false}$

ormap( isprime, { 2, 3, 5, 8 } );

$\mathrm{true}$

t := table( [ a = 1, b = 2, c = 3 ] ):

andmap( type, eval(t,1), 'integer' );

$\mathrm{true}$

andmap( type, eval(t,1), 'even' );

$\mathrm{false}$

ormap( type, eval(t,1), 'even' );

$\mathrm{true}$

e := expand( Int(randpoly(x),x) );

$e≔-7\left(\int x^5\ⅆx\right)+22\left(\int x^4\ⅆx\right)-55\left(\int x^3\ⅆx\right)-94\left(\int x^2\ⅆx\right)+87\left(\int x\ⅆx\right)-56\left(\int 1\ⅆx\right)$

andmap( hastype, e, 'specfunc( anything, Int )' );

$\mathrm{true}$

RecordSlots := proc( r::record )
      if not type( [ args[ 2 .. nargs ] ], 'list( symbol )' ) then
              error "arguments after the first must be of type `symbol'"
      end if;
      andmap( e -> member( cat( e ), r, e ), [ args[ 2 .. nargs ] ] )
end proc:

r := Record( 'a' = 2, 'b' = 3, 'c' = Array( 1 .. 5 ) );

$r≔\mathrm{Record}\left(a=2\,b=3\,c=\left[\begin{array}{ccccc}0& 0& 0& 0& 0\end{array}\right]\right)$

RecordSlots( r, 'a', 'b', 'c' );

$\mathrm{true}$

a, b, c;

$2,3,\left[\begin{array}{ccccc}0& 0& 0& 0& 0\end{array}\right]$

andmap( (a)->`if`( a < 0, FAIL, a mod 7 = 0), [ 7, 14 ] );

$\mathrm{true}$

andmap( (a)->`if`( a < 0, FAIL, a mod 7 = 0), [ 7, 14, -7 ] );

$\mathrm{FAIL}$

andmap( (a)->`if`( a < 0, FAIL, a mod 7 = 0), [ 7, 14, -7, 3 ] );

$\mathrm{false}$

ormap( (a)->`if`( a < 0, FAIL, a mod 7 = 0), [ 7, 14, -7 ] );

$\mathrm{true}$

ormap( (a)->`if`( a < 0, FAIL, a mod 7 = 0), [ 1, 3 ] );

$\mathrm{false}$

ormap( (a)->`if`( a < 0, FAIL, a mod 7 = 0), [ 1, 3, -5 ] );

$\mathrm{FAIL}$

The andmap and ormap commands were updated in Maple 2017.