Browse Source

Internal doc changes for C stack depth options

pull/297/head
Sami Vaarala 9 years ago
parent
commit
e07f5eb7cc
  1. 3
      doc/feature-options.rst
  2. 5
      doc/low-memory.rst
  3. 4
      doc/regexp.rst

3
doc/feature-options.rst

@ -231,6 +231,9 @@ use a deep C stack which relaxes e.g. recursion limits. Automatic feature
detection enables deep C stacks on some platforms known to have them (e.g.
Linux, BSD, Windows).
Removed in Duktape 1.3.0, use explicit config options for shallow stack
targets.
DUK_OPT_NO_REFERENCE_COUNTING
-----------------------------

5
doc/low-memory.rst

@ -69,6 +69,11 @@ Suggested feature options
increases heap header size, it also reduces memory usage fluctuation
which is often more important than absolute footprint.
* If the target has a shallow C stack, you may want to limit C stack
recursion, see:
- ``config/examples/shallow_c_stack.yaml``
* Reduce error handling footprint with one or more of:
- ``DUK_OPT_NO_AUGMENT_ERRORS``

4
doc/regexp.rst

@ -292,7 +292,7 @@ Regexp compiler
C recursion depth limit
The compiler imposes an artificial limit on C recursion depth
(``DUK_RE_COMPILE_RECURSION_LIMIT`` by default). If the recursion limit
(``DUK_USE_REGEXP_COMPILER_RECLIMIT``). If the recursion limit
is reached, regexp compilation fails with an (internal) error.
The following constructs increase C recursion depth:
@ -323,7 +323,7 @@ Regexp executor
C recursion depth limit
The executor imposes an artificial limit on C recursion depth
(``DUK_RE_EXECUTE_RECURSION_LIMIT`` by default). If the recursion limit
(``DUK_USE_REGEXP_EXECUTOR_RECLIMIT``). If the recursion limit
is reached, regexp matching fails with an (internal) error.
The following constructs increase C recursion depth:

Loading…
Cancel
Save