Setting Up External Functions to Be Called from the Wolfram Language

If you have a function defined in an external program, then what you need to do in order to make it possible to call the function from within the Wolfram Language is to add appropriate Wolfram Symbolic Transfer Protocol (WSTP) code that passes arguments to the function and takes back the results it produces.
In simple cases, you can generate the necessary code just by giving an appropriate WSTP template for each external function.
:Function: f
:Pattern: f[x_Integer, y_Integer]
:Arguments: {x, y}
:ArgumentTypes: {Integer, Integer}
:ReturnType: Integer
A file containing a WSTP template for an external function f.
begin the template for a particular function
the name of the function in the external program
the pattern to be defined to call the function
the arguments to the function
the types of the arguments to the function
the type of the value returned by the function
end the template for a particular function
Wolfram Language input to evaluate when the function is installed
The elements of a WSTP template.
Once you have constructed a WSTP template for a particular external function, you have to combine this template with the actual source code for the function. Assuming that the source code is written in the C programming language, you can do this just by adding a line to include the standard WSTP header file, and then inserting a small main program.
Include the standard WSTP header file.
#include "wstp.h"
Here is the actual source code for the function f.
int f(int x, int y) {
return x+y;
This sets up the external program to be ready to take requests from the Wolfram Language.
int main(int argc, char *argv[]) {
return WSMain(argc, argv);
A file f.c containing C source code.
Note that the form of main required on different systems may be slightly different. The release notes included in the WSTP Developer Kit on your particular computer system should give the appropriate form.
preprocess and compile WSTP source files
preprocess WSTP source files
Typical external programs for processing WSTP source files.
WSTP templates are conventionally put in files with names of the form Such files can also contain C source code, interspersed between templates for different functions.
Once you have set up the appropriate files, you then need to process the WSTP template information, and compile all of your source code. Typically you do this by running various external programs, but the details will depend on your computer system.
Under Unix, for example, the WSTP Developer Kit includes a program named wscc that will preprocess WSTP templates in any file whose name ends with .tm, and then call cc on the resulting C source code. wscc will pass commandline options and other files directly to cc.
This preprocesses, then compiles the resulting C source file together with the file f.c.
wscc -o f.exe f.c
This installs the binary in the current Wolfram Language session:
Now calls the external function f(int x, int y) and adds two integers together:
The external program handles only machine integers, so this gives a peculiar result:
On Windows, the WSTP Developer Kit includes a program named mprep, which you have to call directly, giving as input all of the .tm files that you want to preprocess. mprep will generate C source code as output, which you can then feed to a C compiler.
install an external program
uninstall an external program
show active links associated with "prog"
show all active links
show patterns that can be evaluated on a particular link
Handling links to external programs.
This finds the link to the f.exe program:
This shows the Wolfram Language patterns that can be evaluated using the link:
Install sets up the actual function f to execute an appropriate ExternalCall function:
When a WSTP template file is processed, two basic things are done. First, the :Pattern: and specifications are used to generate a Wolfram Language definition that calls an external function via WSTP. And second, the :Function:, and specifications are used to generate C source code that calls your function within the external program.
This gives the name of the actual C function to call in the external program.
:Function:      prog_add
This gives the Wolfram Language pattern for which a definition should be set up.
:Pattern:       SkewAdd[x_Integer, y_Integer:1]
The values of the two list elements are the actual arguments to be passed to the external function.
:Arguments:     {x, If[x > 1, y, y + x - 2]}
This specifies that the arguments should be passed as integers to the C function.
:ArgumentTypes: {Integer, Integer}
This specifies that the return value from the C function will be an integer.
:ReturnType:    Integer
Both the :Pattern: and specifications in a WSTP template can be any Wolfram Language expressions. Whatever you give as the specification will be evaluated every time you call the external function. The result of the evaluation will be used as the list of arguments to pass to the function.
Sometimes you may want to set up Wolfram Language expressions that should be evaluated not when an external function is called, but instead only when the external function is first installed.
You can do this by inserting :Evaluate: specifications in your WSTP template. The expression you give after :Evaluate: can go on for several lines: it is assumed to end when there is first a blank line, or a line that does not begin with spaces or tabs.
This specifies that a usage message for SkewAdd should be set up when the external program is installed.
:Evaluate:    SkewAdd::usage = "SkewAdd[x, y] performs
a skew addition in an external program."
When an external program is installed, the specifications in its WSTP template file are used in the order they were given. This means that any expressions given in :Evaluate: specifications that appear before :Begin: will have been evaluated before definitions for the external function are set up.
Here are Wolfram Language expressions to be evaluated before the definitions for external functions are set up.
:Evaluate:  BeginPackage["XPack`"]
:Evaluate: XF1::usage = "XF1[x, y] is one external function."
:Evaluate: XF2::usage = "XF2[x] is another external function."
:Evaluate: Begin["`Private`"]
This specifies that the function XF1 in the Wolfram Language should be set up to call the function f in the external C program.
:Function: f
:Pattern: XF1[x_Integer, y_Integer]
:Arguments: {x, y}
:ArgumentTypes: {Integer, Integer}
:ReturnType: Integer
This specifies that XF2 in the Wolfram Language should call g. Its argument and return value are taken to be approximate real numbers.
:Function: g
:Pattern: XF2[x_?NumberQ]
:Arguments: {x}
:ArgumentTypes: {Real}
:ReturnType: Real
These Wolfram Language expressions are evaluated after the definitions for the external functions. They end the special context used for the definitions.
:Evaluate:  End[ ]
:Evaluate: EndPackage[ ]
Here is the actual source code for the function f. There is no need for the arguments of this function to have the same names as their Wolfram Language counterparts.
int f(int i, int j) {
return i + j;
Here is the actual source code for g. Numbers that you give in the Wolfram Language will automatically be converted into C double types before being passed to g.
double g(double x) {
return x*x;
By using :Evaluate: specifications, you can evaluate Wolfram Language expressions when an external program is first installed. You can also execute code inside the external program at this time simply by inserting the code in main() before the call to WSMain(). This is sometimes useful if you need to initialize the external program before any functions in it are used.
evaluate a string as Wolfram Language input
Executing a command in the Wolfram Language from within an external program.
int diff(int i, int j) {
This evaluates a Wolfram Language Print function if i < j.
    if (i < j) WSEvaluateString(stdlink, "Print[\"negative\"]");
return i - j;
This installs an external program containing the diff function defined above:
Calling diff causes Print to be executed:
Note that any results generated in the evaluation requested by WSEvaluateString() are ignored. To make use of such results requires full twoway communication between the Wolfram Language and external programs, as discussed in "Two-Way Communication with External Programs".