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

Updates documentation to 0.7.0.

Browse Source
This commit is contained in:
Erik Kundt
2020-01-10 18:56:38 +01:00
parent 2c478e85e2
commit fe1676203d
33 changed files with 127 additions and 127 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/control-structures.rst
+13 -13
View File
@@ -41,7 +41,7 @@ Internal Function Calls
Functions of the current contract can be called directly ("internally"), also recursively, as seen in
this nonsensical example::
pragma solidity >=0.4.16 <0.7.0;
pragma solidity >=0.4.16 <0.8.0;
contract C {
function g(uint a) public pure returns (uint ret) { return a + f(); }
@@ -81,7 +81,7 @@ of the contract:
::
pragma solidity >=0.4.0 <0.7.0;
pragma solidity >=0.4.0 <0.8.0;
contract InfoFeed {
function info() public payable returns (uint ret) { return 42; }
@@ -131,7 +131,7 @@ parameters from the function declaration, but can be in arbitrary order.
::
pragma solidity >=0.4.0 <0.7.0;
pragma solidity >=0.4.0 <0.8.0;
contract C {
mapping(uint => uint) data;
@@ -154,7 +154,7 @@ Those parameters will still be present on the stack, but they are inaccessible.
::
pragma solidity >=0.4.16 <0.7.0;
pragma solidity >=0.4.16 <0.8.0;
contract C {
// omitted name for parameter
@@ -177,7 +177,7 @@ is compiled so recursive creation-dependencies are not possible.
::
pragma solidity >=0.5.0 <0.7.0;
pragma solidity >=0.5.0 <0.8.0;
contract D {
uint public x;
@@ -237,7 +237,7 @@ groupings of expressions.
::
pragma solidity >0.4.23 <0.7.0;
pragma solidity >0.4.23 <0.8.0;
contract C {
uint index;
@@ -292,7 +292,7 @@ because only a reference and not a copy is passed.
::
pragma solidity >=0.4.16 <0.7.0;
pragma solidity >=0.4.16 <0.8.0;
contract C {
uint[20] x;
@@ -350,7 +350,7 @@ the two variables have the same name but disjoint scopes.
::
pragma solidity >=0.5.0 <0.7.0;
pragma solidity >=0.5.0 <0.8.0;
contract C {
function minimalScoping() pure public {
{
@@ -371,7 +371,7 @@ In any case, you will get a warning about the outer variable being shadowed.
::
pragma solidity >=0.5.0 <0.7.0;
pragma solidity >=0.5.0 <0.8.0;
// This will report a warning
contract C {
function f() pure public returns (uint) {
@@ -392,7 +392,7 @@ In any case, you will get a warning about the outer variable being shadowed.
::
pragma solidity >=0.5.0 <0.7.0;
pragma solidity >=0.5.0 <0.8.0;
// This will not compile
contract C {
function f() pure public returns (uint) {
@@ -480,7 +480,7 @@ and ``assert`` for internal error checking.
::
pragma solidity >=0.5.0 <0.7.0;
pragma solidity >=0.5.0 <0.8.0;
contract Sharer {
function sendHalf(address payable addr) public payable returns (uint balance) {
@@ -524,7 +524,7 @@ The following example shows how to use an error string together with ``revert``
::
pragma solidity >=0.5.0 <0.7.0;
pragma solidity >=0.5.0 <0.8.0;
contract VendingMachine {
function buy(uint amount) public payable {
@@ -567,7 +567,7 @@ A failure in an external call can be caught using a try/catch statement, as foll
::
pragma solidity ^0.6.0;
pragma solidity >=0.6.0 <0.8.0;
interface DataFeed { function getData(address token) external returns (uint value); }