Maple Professional
Maple Academic
Maple Student Edition
Maple Personal Edition
Maple Player
Maple Player for iPad
MapleSim Professional
MapleSim Academic
Maple T.A. - Testing & Assessment
Maple T.A. MAA Placement Test Suite
Möbius - Online Courseware
Machine Design / Industrial Automation
Aerospace
Vehicle Engineering
Robotics
Power Industries
System Simulation and Analysis
Model development for HIL
Plant Modeling for Control Design
Robotics/Motion Control/Mechatronics
Other Application Areas
Mathematics Education
Engineering Education
High Schools & Two-Year Colleges
Testing & Assessment
Students
Financial Modeling
Operations Research
High Performance Computing
Physics
Live Webinars
Recorded Webinars
Upcoming Events
MaplePrimes
Maplesoft Blog
Maplesoft Membership
Maple Ambassador Program
MapleCloud
Technical Whitepapers
E-Mail Newsletters
Maple Books
Math Matters
Application Center
MapleSim Model Gallery
User Case Studies
Exploring Engineering Fundamentals
Teaching Concepts with Maple
Maplesoft Welcome Center
Teacher Resource Center
Student Help Center
type/procedure - check for a procedure
Calling Sequence
type(expr, 'procedure')
type(expr, 'procedure[rtype](type1, type2, ...)')
Parameters
expr
-
any expression
rtype, type1, type2, ...
any Maple types
Description
The first form of this command performs a surface type test for expressions of type procedure. This includes both builtin and library- or user-defined procedures. See ?procedure for more information about the definition and use of procedures.
Note the distinction between an expression of type procedure and one of type function, which might be better called a ``function call''. In Maple it is the ``procedure'' type, rather than ``function'' that corresponds to what one thinks of as a ``mathematical function''.
The second form of test is a structured type test for procedures whose arguments and (optionally) return types are ``declared'' to have a given type. (The term ``declared'' is a misnomer, since one of Maple's strengths is its complete lack of type declarations. However, for the purpose of dynamic type checking, it is useful to think of argument type specifier and return type assertion annotations in this way.)
A ``declared'' return type may be tested for by enclosing the type specifier rtype (which may be an arbitrary Maple type) for the return type in brackets immediately after the symbol procedure. Procedures that do not have a return type assertion are considered to have a declared return type of anything.
Explicitly ``declared'' parameter types may be tested for by enclosing the types in parentheses. The names of parameters are not considered, only their ``declared'' types. A procedure p has type procedure(T1, T2, ..., Tn), where T1, T2, ..., Tn are types, if it has exactly n ``declared'' parameters and the i-th parameter is ``declared'' to have type Ti, for each i. In other words, p must have been defined by a procedure definition of the form p := proc(t1::T1, t2::T2, ..., tn::Tn). A parameter whose type is not specified is considered to have been ``declared'' to have type anything.
Note that argument types and return types are both optional and may be tested independently of one another.
Currently, argument and return types must match exactly the types found in the procedure data structure. Subtype relationships are not computed.
Note that no builtin procedure has either return type assertions or ``declared'' parameter types.
Examples
The first few examples try to illustrate the sometimes confusing relationship between procedures and functions.
Here are some examples of various kinds of procedures, and some non-examples.
f := proc(x) x^2 end proc;
These examples illustrate the use of the structured procedure type.
p := proc( a::algebraic, n::integer)::algebraic; a^n end proc:
p := proc( a::algebraic, n::integer) a^n end proc: # no return type assertion
See Also
procedure, type, type/anything, type/appliable, type/builtin, type/function, type/last_name_eval, type/operator
Download Help Document