Did you know ... Search Documentation:
GIT commit info
Describe stack limit handling
authorJan Wielemaker
Thu Jul 19 21:19:53 2018 +0200
committerJan Wielemaker
Thu Jul 19 21:20:53 2018 +0200
commit7d845e9b0fa61f1b6703c082217d0a92debe02eb
tree449a0a1552788d58ae65bc4ee8bb99c06db9b6cc
parent123724a719b56bb6b69b54dd29358fb7ace097ca
Diff style: patch stat
diff --git a/changes/stack-limit.txt b/changes/stack-limit.txt
new file mode 100644
index 0000000..23caf49
--- /dev/null
+++ b/changes/stack-limit.txt
@@ -0,0 +1,19 @@
+# Stack limit handling
+
+Older versions of SWI-Prolog had individual limits for all three (local,
+global and trail) stacks that were controlled using set_prolog_stack/2
+as well as the command line options `-L`, `-G` and `-T`.
+
+In recent version the stack limit is controlled by a single limit per
+thread that is controlled by the Prolog flag `stack_limit` and the
+command line argument `--stack_limit=size`, where `size` is a number
+that is optionally postfixed with one of `BKMG` for _bytes_, _Kbytes_
+_Mbytes_ or _Gbytes_.
+
+Calls to set_prolog_stack/2 that set the limit are translated to setting
+the Prolog flag and printing a _deprecated_ warning.
+
+Note that using a flag implies that new threads inherit the limit from
+the thread that creates the new thread. In old versions new threads
+always started with the default limits or the limits provided at the
+command line.