summaryrefslogtreecommitdiff
path: root/system/doc/reference_manual/features.xml
diff options
context:
space:
mode:
Diffstat (limited to 'system/doc/reference_manual/features.xml')
-rw-r--r--system/doc/reference_manual/features.xml22
1 files changed, 8 insertions, 14 deletions
diff --git a/system/doc/reference_manual/features.xml b/system/doc/reference_manual/features.xml
index 882cdd2582..e3b12742c6 100644
--- a/system/doc/reference_manual/features.xml
+++ b/system/doc/reference_manual/features.xml
@@ -4,7 +4,7 @@
<chapter>
<header>
<copyright>
- <year>2022</year><year>2022</year>
+ <year>2022</year><year>2023</year>
<holder>Ericsson AB. All Rights Reserved.</holder>
</copyright>
<legalnotice>
@@ -150,19 +150,13 @@
enable|disable)</c></seeguide> directive. This is the preferred
method of enabling and disabling features.</item>
</taglist>
- <p>
- Note that to load a module compiled with features enabled, the
- corresponding features must be enabled in the runtime. This
- is done using options <seecom
- marker="erts:erl#enable-feature"><c>-enable-feature</c></seecom>
- and <seecom
- marker="erts:erl#disable-feature"><c>-disable-feature</c></seecom>
- to <c>erl</c>. This is to allow the possibility to prevent
- the use of experimental features in, e.g., production. This
- will catch experimental features used in both own and third
- party components. An active choice to use experimental
- features must be done.
- </p>
+ <change>
+ <p>In Erlang/OTP 25, in order to load a module with a feature
+ enabled, it was necessary to also enable the feature in the runtime.
+ This was done using option <seecom
+ marker="erts:erl#enable-feature"><c>-enable-feature</c></seecom> to
+ <c>erl</c>. This requirement was removed in Erlang/OTP 26.</p>
+ </change>
</section>
<section>