summaryrefslogtreecommitdiff
path: root/blog/stem.org
diff options
context:
space:
mode:
authorPreston Pan <ret2pop@nullring.xyz>2026-03-04 17:17:01 -0800
committerPreston Pan <ret2pop@nullring.xyz>2026-03-04 17:17:01 -0800
commite362835b1b186a9a33f1ac32e59778ed5b2549d8 (patch)
tree30762444a6452c866107e8b696efe509c61e7601 /blog/stem.org
parentcf6822db165df6c09e1b64349cb01d2c2d90effd (diff)
remove remaining dead links
Diffstat (limited to 'blog/stem.org')
-rw-r--r--blog/stem.org3
1 files changed, 0 insertions, 3 deletions
diff --git a/blog/stem.org b/blog/stem.org
index ba65a4e..62a140b 100644
--- a/blog/stem.org
+++ b/blog/stem.org
@@ -20,7 +20,6 @@ and objects from the foreign language interface by writing C libraries.
If you don't know what any of that means, that is okay. I will go over the programming language as if this
is your first programming language, as stem is one of the most simple programming languages
that is feasible for practical use. For information on how to install stem on MacOS or Linux, see [[https://github.com/ret2pop/stem][the github page]].
-Documentation on the C API is available on the [[https://stemdoc.nullring.xyz][Doxygen generated page]].
* Language Design
In stem, all information is stored on what's called /the stack/, and there are things that you can put on the stack.
@@ -394,5 +393,3 @@ The builtin word ~clib~ loads a library dynamically and calls both ~add_func~ an
Note that when making custom functions, they must be in the form ~void my_func(void *value)~, where ~value~ contains the word that is used to call the function. When you
are implementing functions, make sure to keep only one copy of a pointer on the stack at all times, otherwise it is prone to segfaulting. Also, for examples on how builtins
may be implemented, see ~builtins.c~.
-
-Again, you can view the API at the [[https://stemdoc.nullring.xyz][webpage generated by doxygen]].