cerc-io/solidity
16
0
Fork 0
mirror of https://github.com/ethereum/solidity synced 2023-10-03 13:03:40 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #667 from fabioberger/patch-1

Browse Source 
Documentation Typos
This commit is contained in:
chriseth 2016-06-19 11:00:39 +02:00 committed by GitHub
commit 5917c8e7da
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/miscellaneous.rst
View File

@ -161,7 +161,7 @@ Unfortunately, there are some subtleties the compiler does not yet warn you abou
2. Sending Ether can fail due to the call depth going above 1024. Since the caller is in total control of the call 2. Sending Ether can fail due to the call depth going above 1024. Since the caller is in total control of the call
depth, they can force the transfer to fail, so make sure to always check the return value of ``send``. Better yet, depth, they can force the transfer to fail, so make sure to always check the return value of ``send``. Better yet,
write your contract using a pattern where the recipient can withdraw Ether instead. write your contract using a pattern where the recipient can withdraw Ether instead.
3. Sending Ether can also fail because the recipient goes out of gas (either explicitly by using ``throw`` or 3. Sending Ether can also fail because the recipient runs out of gas (either explicitly by using ``throw`` or
because the operation is just too expensive). If the return value of ``send`` is checked, this might provide a because the operation is just too expensive). If the return value of ``send`` is checked, this might provide a
means for the recipient to block progress in the sending contract. Again, the best practise here is to use means for the recipient to block progress in the sending contract. Again, the best practise here is to use
a "withdraw" pattern instead of a "send" pattern. a "withdraw" pattern instead of a "send" pattern.

2
docs/types.rst
View File

@ -10,7 +10,7 @@ Solidity is a statically typed language, which means that the type of each
variable (state and local) needs to be specified (or at least known - variable (state and local) needs to be specified (or at least known -
see :ref:`type-deduction` below) at see :ref:`type-deduction` below) at
compile-time. Solidity provides several elementary types which can be combined compile-time. Solidity provides several elementary types which can be combined
to complex types. to form complex types.
.. index:: ! value type, ! type;value .. index:: ! value type, ! type;value