From a3af5f4a5c4568225ef91ee4493da6bf659f7161 Mon Sep 17 00:00:00 2001
From: Lukas Larsson <lukas@erlang-solutions.com>
Date: Mon, 2 Sep 2013 17:27:58 +0200
Subject: erts: Set default external enc to use new float scheme

This change was triggered by the OSE float printing function
not working exactly the same way as linux/win32. But it is
also a good one in general as it cuts size in more than half
for floats.
---
 erts/doc/src/erlang.xml | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

(limited to 'erts/doc/src')

diff --git a/erts/doc/src/erlang.xml b/erts/doc/src/erlang.xml
index 0f312fb430..accd7f0b08 100644
--- a/erts/doc/src/erlang.xml
+++ b/erts/doc/src/erlang.xml
@@ -6572,11 +6572,12 @@ ok
           some details of the encoding. This option was
           introduced in R11B-4. Currently, the allowed values for <c><anno>Version</anno></c>
           are <c>0</c> and <c>1</c>.</p>
-        <p><c>{minor_version, 1}</c> forces any floats in the term to be encoded
+        <p><c>{minor_version, 1}</c> is since 17.0 the default, it forces any floats in
+	  the term to be encoded
           in a more space-efficient and exact way (namely in the 64-bit IEEE format,
           rather than converted to a textual representation). <c>binary_to_term/1</c>
-          in R11B-4 and later is able decode the new representation.</p>
-        <p><c>{minor_version, 0}</c> is currently the default, meaning that floats
+          in R11B-4 and later is able decode this representation.</p>
+        <p><c>{minor_version, 0}</c> meaning that floats
           will be encoded using a textual representation; this option is useful if
           you want to ensure that releases prior to R11B-4 can decode resulting
           binary.</p>
-- 
cgit v1.2.3