Internals: Adding a Function in Engine, Interpreter, and Core
Work in progress. Contributors: Michael Burr, (your-name-here)
History: The engine is based on an old version of C++. The engine was originally designed to be fast and to include only the most important things. It has been growing in size since then to include more.
Project: Modernize the engine
Structure: The engine consists of three parts:
-
The engine (C++ code). This is contained in the e directory.
-
The interface (d/dd). This is contained in the d directory. The file interface.dd connects actual functions to the m2 interpreter functions. (Here, d connects to C code while dd connects to C++ code).
-
The M2 code.
Parts 1. and 2. compile to executable.
Provides C/C++ functions that the top level Macaulay2 code can call. Most of the code is contained in files x-<FileName>.cpp files. The functions should be named raw<FunctionName> (not within a namespace). The raw<FunctionName> and arguments should be in the engine.h header and the source code in an x-<FileName>.cpp file. Recompile after adding changes.
Add the function to connect the Macaulay2 to the raw function. Start with the command export <rawFunctionName>(e:Expr):Expr := (...); Then, perform tests to determine when e is the right type of object, e.g., the length and properties of e. Use toExpr(...) to make the actual C/C++ call. The details of the toExpr(...) call are toExpr(Ccode(<return type>,"raw<FunctionName>(",<arguments separated by commas and ","'s, ")">;. Exceptions should be raised using functions of the form WrongArg<Error Type>(...). Finally, use setupfun("<M2 language name>",<rawFunctionName>); The functions need to be exported so that you can use in another d file, otherwise, no export is needed.
Potential Confusion: There are three names which are often all the same (but not required). The function setupfun connects the name from within M2 to the function in interface.dd. The function toExpr makes the call to the engine.
Side Note: See parse.d for the lengthy definition of Expr.
Macaulay2 can call the name from interface.dd to run the code. Often these are used within an M2 functions to hide the underlying C/C++ code.
Accessing Functions: There are a few main ways to access the functions created in the interface.
-
Start with debug Core in M2. Then, the function can be accessed directly. Alternately,
-
Assign the function directly with raw<function name> = value Core#"private dictionary"#<Function name>
Side Notes: There are also raw versions of data types which can be explored (with debug Core). There are alternate ways to access the functions, but the approaches above include more data about the functions.
