aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--docs/frequently-asked-questions.rst5
-rw-r--r--docs/types.rst6
2 files changed, 6 insertions, 5 deletions
diff --git a/docs/frequently-asked-questions.rst b/docs/frequently-asked-questions.rst
index 5f1a981e..d9a68ed1 100644
--- a/docs/frequently-asked-questions.rst
+++ b/docs/frequently-asked-questions.rst
@@ -103,11 +103,6 @@ This is a limitation of the EVM and will be solved with the next protocol update
Returning variably-sized data as part of an external transaction or call is fine.
-How do you represent ``double``/``float`` in Solidity?
-======================================================
-
-This is not yet possible.
-
Is it possible to in-line initialize an array like so: ``string[] myarray = ["a", "b"];``
=========================================================================================
diff --git a/docs/types.rst b/docs/types.rst
index d1b5a3f1..71a4b0e6 100644
--- a/docs/types.rst
+++ b/docs/types.rst
@@ -88,6 +88,12 @@ Operators:
* Comparisons: ``<=``, ``<``, ``==``, ``!=``, ``>=``, ``>`` (evaluate to ``bool``)
* Arithmetic operators: ``+``, ``-``, unary ``-``, unary ``+``, ``*``, ``/``, ``%`` (remainder)
+.. note::
+ The main difference between floating point (``float`` and ``double`` in many languages, more precisely IEEE 754 numbers) and fixed point numbers is
+ that the number of bits used for the integer and the fractional part (the part after the decimal dot) is flexible in the former, while it is strictly
+ defined in the latter. Generally, in floating point almost the entire space is used to represent the number, while only a small number of bits define
+ where the decimal point is.
+
.. index:: address, balance, send, call, callcode, delegatecall, transfer
.. _address: