andmap
determine whether a predicate is true of all operands of an expression
ormap
determine whether a predicate is true of some operands of an expression
Calling Sequence
Parameters
Description
Thread Safety
Examples
Compatibility
andmap(p, expr, ...)
ormap(p, expr, ...)
p
-
predicate returning either true or false
expr
expression
...
(optional) other arguments to pass to p
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' );
true
ormap( type, [ 1, 2, 3, 4, 5 ], 'integer' );
andmap( type, [ 1, 2, 3, 4, 5 ], 'even' );
false
ormap( type, [ 1, 2, 3, 4, 5 ], 'even' );
andmap( isprime, [ 2, 3, 5, 7 ] );
andmap( isprime, [ 2, 3, 5, 8 ] );
ormap( isprime, { 2, 3, 5, 8 } );
t := table( [ a = 1, b = 2, c = 3 ] ):
andmap( type, eval(t,1), 'integer' );
andmap( type, eval(t,1), 'even' );
ormap( type, eval(t,1), 'even' );
e := expand( Int(randpoly(x),x) );
e≔−7⁢∫x5ⅆx+22⁢∫x4ⅆx−55⁢∫x3ⅆx−94⁢∫x2ⅆx+87⁢∫xⅆx−56⁢∫1ⅆx
andmap( hastype, e, 'specfunc( anything, Int )' );
This examples illustrates a technique for quickly destructuring a record.
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≔Record⁡a=2,b=3,c=00000
RecordSlots( r, 'a', 'b', 'c' );
a, b, c;
2,3,00000
andmap( (a)->`if`( a < 0, FAIL, a mod 7 = 0), [ 7, 14 ] );
andmap( (a)->`if`( a < 0, FAIL, a mod 7 = 0), [ 7, 14, -7 ] );
FAIL
andmap( (a)->`if`( a < 0, FAIL, a mod 7 = 0), [ 7, 14, -7, 3 ] );
ormap( (a)->`if`( a < 0, FAIL, a mod 7 = 0), [ 7, 14, -7 ] );
ormap( (a)->`if`( a < 0, FAIL, a mod 7 = 0), [ 1, 3 ] );
ormap( (a)->`if`( a < 0, FAIL, a mod 7 = 0), [ 1, 3, -5 ] );
The andmap and ormap commands were updated in Maple 2017.
See Also
curry
map
op
rcurry
select
spec_eval_rules
StringTools
StringTools[AndMap]
StringTools[OrMap]
type/atomic
Download Help Document
What kind of issue would you like to report? (Optional)