cerc-io/solidity
10
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

Add note about throw being deprecated

Browse Source
This commit is contained in:
Alex Beregszaszi 2017-08-28 12:03:39 +01:00
parent 2b26d6b9d7
commit 5a5d21d0c8
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/control-structures.rst
View File

@ -389,6 +389,9 @@ There are two other ways to trigger exceptions: The ``revert`` function can be u
revert the current call. In the future it might be possible to also include details about the error revert the current call. In the future it might be possible to also include details about the error
in a call to ``revert``. The ``throw`` keyword can also be used as an alternative to ``revert()``. in a call to ``revert``. The ``throw`` keyword can also be used as an alternative to ``revert()``.
.. note::
From version 0.4.13 the ``throw`` keyword is deprecated and will be phased out in the future.
When exceptions happen in a sub-call, they "bubble up" (i.e. exceptions are rethrown) automatically. Exceptions to this rule are ``send`` When exceptions happen in a sub-call, they "bubble up" (i.e. exceptions are rethrown) automatically. Exceptions to this rule are ``send``
and the low-level functions ``call``, ``delegatecall`` and ``callcode`` -- those return ``false`` in case and the low-level functions ``call``, ``delegatecall`` and ``callcode`` -- those return ``false`` in case
of an exception instead of "bubbling up". of an exception instead of "bubbling up".