aboutsummaryrefslogtreecommitdiffstats
path: root/system/doc/efficiency_guide
diff options
context:
space:
mode:
authorBjörn Gustavsson <[email protected]>2017-01-10 14:53:03 +0100
committerBjörn Gustavsson <[email protected]>2017-01-10 14:53:03 +0100
commit947169af61bdd67d34fabd47a56be04e8468120d (patch)
tree9130c98b141e9fca373c6fcf8fe2e463838e8198 /system/doc/efficiency_guide
parent9595a90fd301e2049b822c8a4d712b5033a3e9d0 (diff)
downloadotp-947169af61bdd67d34fabd47a56be04e8468120d.tar.gz
otp-947169af61bdd67d34fabd47a56be04e8468120d.tar.bz2
otp-947169af61bdd67d34fabd47a56be04e8468120d.zip
Remove mention of R12B
Also don't say that there are no plans to make sharing-preserving copying default; it has been seriously suggested.
Diffstat (limited to 'system/doc/efficiency_guide')
-rw-r--r--system/doc/efficiency_guide/processes.xml10
1 files changed, 4 insertions, 6 deletions
diff --git a/system/doc/efficiency_guide/processes.xml b/system/doc/efficiency_guide/processes.xml
index f2d9712f51..bc9daa6666 100644
--- a/system/doc/efficiency_guide/processes.xml
+++ b/system/doc/efficiency_guide/processes.xml
@@ -146,14 +146,14 @@ loop() ->
<section>
<title>Constant Pool</title>
- <p>Constant Erlang terms (also called <em>literals</em>) are now
+ <p>Constant Erlang terms (also called <em>literals</em>) are
kept in constant pools; each loaded module has its own pool.
- The following function does no longer build the tuple every time
+ The following function does not build the tuple every time
it is called (only to have it discarded the next time the garbage
collector was run), but the tuple is located in the module's
constant pool:</p>
- <p><em>DO</em> (in R12B and later)</p>
+ <p><em>DO</em></p>
<code type="erl">
days_in_month(M) ->
element(M, {31,28,31,30,31,30,31,31,30,31,30,31}).</code>
@@ -235,9 +235,7 @@ true
return the same value. Sharing has been lost.</p>
<p>In a future Erlang/OTP release, it might be implemented a
- way to (optionally) preserve sharing. There are no plans to make
- preserving of sharing the default behaviour, as that would
- penalize the vast majority of Erlang applications.</p>
+ way to (optionally) preserve sharing.</p>
</section>
</section>