Merge branch 'bg/efficiency-guide' into dev

* bg/efficiency-guide:
  Efficiency Guide: Recommend external funs over tuple funs
  Efficiency Guide: The maximum number of atoms can be configured
  Efficiency Guide: Fix typos

OTP-8515 bg/efficiency-guide

4 files changed, 18 insertions, 15 deletions

diff --git a/system/doc/efficiency_guide/advanced.xml b/system/doc/efficiency_guide/advanced.xml
index 0ec3afbd59..7898f925b9 100644
--- a/system/doc/efficiency_guide/advanced.xml
+++ b/system/doc/efficiency_guide/advanced.xml
@@ -4,7 +4,7 @@
 <chapter>
   <header>
     <copyright>
-      <year>2001</year><year>2009</year>
+      <year>2001</year><year>2010</year>
       <holder>Ericsson AB. All Rights Reserved.</holder>
     </copyright>
     <legalnotice>
@@ -13,12 +13,12 @@
       compliance with the License. You should have received a copy of the
       Erlang Public License along with this software. If not, it can be
       retrieved online at http://www.erlang.org/.
-    
+
       Software distributed under the License is distributed on an "AS IS"
       basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See
       the License for the specific language governing rights and limitations
       under the License.
-    
+
     </legalnotice>
 
     <title>Advanced</title>
@@ -154,7 +154,8 @@ On 64-bit architectures: 4 words for a reference from the current local node, an
       <item>255</item>
       <tag><em>Atoms </em></tag>
       <item>      <marker id="atoms"></marker>
-The maximum number of atoms is 1048576. </item>
+	By default, the maximum number of atoms is 1048576.
+	This limit can be raised or lowered using the <c>+t</c> option.</item>
       <tag><em>Ets-tables</em></tag>
       <item>The default is 1400, can be changed with the environment variable <c>ERL_MAX_ETS_TABLES</c>.</item>
       <tag><em>Elements in a tuple</em></tag>
@@ -175,7 +176,7 @@ The maximum number of atoms is 1048576. </item>
       <tag><em>Total amount of data allocated by an Erlang node</em></tag>
       <item>The Erlang runtime system can use the complete 32 (or 64) bit address space,
        but the operating system often limits a single process to use less than that.</item>
-      <tag><em>length of a node name</em></tag>
+      <tag><em>Length of a node name</em></tag>
       <item>An Erlang node name has the form host@shortname or host@longname. The node name is 
        used as an atom within the system so the maximum size of 255 holds for the node name too.</item>
       <tag><em>Open ports</em></tag>
diff --git a/system/doc/efficiency_guide/commoncaveats.xml b/system/doc/efficiency_guide/commoncaveats.xml
index e18e5aa510..61d13636c0 100644
--- a/system/doc/efficiency_guide/commoncaveats.xml
+++ b/system/doc/efficiency_guide/commoncaveats.xml
@@ -4,7 +4,7 @@
 <chapter>
   <header>
     <copyright>
-      <year>2001</year><year>2009</year>
+      <year>2001</year><year>2010</year>
       <holder>Ericsson AB. All Rights Reserved.</holder>
     </copyright>
     <legalnotice>
@@ -13,12 +13,12 @@
       compliance with the License. You should have received a copy of the
       Erlang Public License along with this software. If not, it can be
       retrieved online at http://www.erlang.org/.
-    
+
       Software distributed under the License is distributed on an "AS IS"
       basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See
       the License for the specific language governing rights and limitations
       under the License.
-    
+
     </legalnotice>
 
     <title>Common Caveats</title>
@@ -69,7 +69,7 @@
 
     <p>Atoms are not garbage-collected. Once an atom is created, it will never
     be removed. The emulator will terminate if the limit for the number
-    of atoms (1048576) is reached.</p>
+    of atoms (1048576 by default) is reached.</p>
 
     <p>Therefore, converting arbitrary input strings to atoms could be
     dangerous in a system that will run continuously.
diff --git a/system/doc/efficiency_guide/functions.xml b/system/doc/efficiency_guide/functions.xml
index d55b60e39c..fe14a4f000 100644
--- a/system/doc/efficiency_guide/functions.xml
+++ b/system/doc/efficiency_guide/functions.xml
@@ -4,7 +4,7 @@
 <chapter>
   <header>
     <copyright>
-      <year>2001</year><year>2009</year>
+      <year>2001</year><year>2010</year>
       <holder>Ericsson AB. All Rights Reserved.</holder>
     </copyright>
     <legalnotice>
@@ -13,12 +13,12 @@
       compliance with the License. You should have received a copy of the
       Erlang Public License along with this software. If not, it can be
       retrieved online at http://www.erlang.org/.
-    
+
       Software distributed under the License is distributed on an "AS IS"
       basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See
       the License for the specific language governing rights and limitations
       under the License.
-    
+
     </legalnotice>
 
     <title>Functions</title>
@@ -179,7 +179,9 @@ explicit_map_pairs(Map, Xs0, Ys0) ->
        A "tuple fun", <c>{Module,Function}</c>, is not a fun.
        The cost for calling a "tuple fun" is similar to that
        of <c>apply/3</c> or worse. Using "tuple funs" is <em>strongly discouraged</em>,
-       as they may not be supported in a future release.</p></warning>
+       as they may not be supported in a future release,
+       and because there exists a superior alternative since the R10B
+       release, namely the <c>fun Module:Function/Arity</c> syntax.</p></warning>
 
        <p><c>apply/3</c> must look up the code for the function to execute
        in a hash table. Therefore, it will always be slower than a
diff --git a/system/doc/efficiency_guide/myths.xml b/system/doc/efficiency_guide/myths.xml
index 76a72368bb..65113c9372 100644
--- a/system/doc/efficiency_guide/myths.xml
+++ b/system/doc/efficiency_guide/myths.xml
@@ -168,8 +168,8 @@ vanilla_reverse([], Acc) ->
     <p>Actually, string handling could be slow if done improperly.
     In Erlang, you'll have to think a little more about how the strings
     are used and choose an appropriate representation and use
-    the <seealso marker="stdlib:re">re</seealso> instead of the obsolete
-    <c>regexp</c> module if you are going to use regualr expressions.</p>
+    the <seealso marker="stdlib:re">re</seealso> module instead of the obsolete
+    <c>regexp</c> module if you are going to use regular expressions.</p>
   </section>
 
   <section>