Funk2 currently compiles on 32-bit and 64-bit Linux operating systems. 64-bit pointers are recommended because of the amount of memory needed for the reflective capabilities; a 32-bit machine is currently only able to index a few gigabytes of memory.

The goal of the programming language Funk2 is to enable reflective algorithmic tracing for large heterogenous control systems. A few point emphasized in the Funk2 programming language are:

Examples of the most basic computational features include: (1) memory creation, (2) memory read, and (3) memory write. Tracing all causal relationships between these basic features allows tracing the context of all other programmer-defined semantic abstractions. All of these computational features create an intricate trace network of dependencies, automatically traceable and shared by many parallel threads of execution. Funk2 allows causal tracing to occur modularly to dynamically chosen parts of large commonsense-scale artificial intelligence projects. The resulting causal dependency trace networks can be processed by critical causal reflection threads.

Here is how to retrieve the creation Cause for any piece of memory ([], the value of the symbol nil, is the only thing that does not reference a piece of memory):

Note that in the Cause object there are multiple named slots holding information in the frame of the cause. The frames of a Cause are thread, env, name, and args. By default only 7 levels of recursion are printed to the screen. The symbol used for ending a recursion is the astrisk, *.In order to access the slots of an object, you can use funktions that are named to access and mutate objects. For example, the following example shows how to retrieve only the name and args slots of a cause object.

Here is an example of how to remember the state of an object at specific historical points in time:

Here is another example of how to remember the state of an object at specific historical points in time:

Here is one straightforward way to write a "Hello world!" program in the Funk2 language:

Here is another more advanced way to holla your planet:

Here is how to define and subsequently call a funktion:

Here is how to loop over a list of values:

Here is how to call our funktion above in a parallel thread:

Here is how to serially filter every element in a list:

Here is how to concurrently filter every element in a list:

The scheduler:global_scheduler variable in the global environment can be used as a reference to the global funk2 scheduler for the local machine. Processor information available from "/dev/proc" during funk2 initial bootstrap compile is available for all machines currently logged into the grid. Grid support is in development, this only shows this information for the local machine. Once support for multiple machines is available, this variable will change into a funktion that takes a machine-id as an argument and returns that machine's scheduler object.