aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChris Ward <chris.ward@ethereum.org>2019-01-03 00:25:16 +0800
committerChris Ward <chris.ward@ethereum.org>2019-01-07 21:20:10 +0800
commitcefc6c433e1722364a1461a144b077e57e2ecafe (patch)
treeccb81630ace0da0ba436d6084d259f188ad90bf3
parentaca9e581454585fab494a87febb7da3278e3aa7b (diff)
downloaddexon-solidity-cefc6c433e1722364a1461a144b077e57e2ecafe.tar.gz
dexon-solidity-cefc6c433e1722364a1461a144b077e57e2ecafe.tar.zst
dexon-solidity-cefc6c433e1722364a1461a144b077e57e2ecafe.zip
Update non-existant pragma 0.4.99 to 0.5.0
Use correct syntax for pragma Change pragma syntax One more change to pragma syntax
-rw-r--r--docs/050-breaking-changes.rst8
-rw-r--r--docs/abi-spec.rst2
-rw-r--r--docs/common-patterns.rst4
-rw-r--r--docs/contracts.rst14
-rw-r--r--docs/control-structures.rst12
-rw-r--r--docs/frequently-asked-questions.rst2
-rw-r--r--docs/introduction-to-smart-contracts.rst2
-rw-r--r--docs/security-considerations.rst4
8 files changed, 24 insertions, 24 deletions
diff --git a/docs/050-breaking-changes.rst b/docs/050-breaking-changes.rst
index 32241776..01d21c8c 100644
--- a/docs/050-breaking-changes.rst
+++ b/docs/050-breaking-changes.rst
@@ -308,7 +308,7 @@ This will no longer compile with Solidity v0.5.0. However, you can define a comp
::
- pragma solidity >0.4.99 <0.6.0;
+ pragma solidity ^0.5.0;
interface OldContract {
function someOldFunction(uint8 a) external;
function anotherOldFunction() external returns (bool);
@@ -325,7 +325,7 @@ Given the interface defined above, you can now easily use the already deployed p
::
- pragma solidity >0.4.99 <0.6.0;
+ pragma solidity ^0.5.0;
interface OldContract {
function someOldFunction(uint8 a) external;
@@ -345,7 +345,7 @@ commandline compiler for linking):
::
- pragma solidity >0.4.99 <0.6.0;
+ pragma solidity ^0.5.0;
library OldLibrary {
function someFunction(uint8 a) public returns(bool);
@@ -430,7 +430,7 @@ New version:
::
- pragma solidity >0.4.99 <0.6.0;
+ pragma solidity ^0.5.0;
contract OtherContract {
uint x;
diff --git a/docs/abi-spec.rst b/docs/abi-spec.rst
index 2c01c4a1..68ca8ec4 100644
--- a/docs/abi-spec.rst
+++ b/docs/abi-spec.rst
@@ -471,7 +471,7 @@ For example,
::
- pragma solidity >0.4.99 <0.6.0;
+ pragma solidity ^0.5.0;
contract Test {
constructor() public { b = hex"12345678901234567890123456789012"; }
diff --git a/docs/common-patterns.rst b/docs/common-patterns.rst
index 84c18936..3704b730 100644
--- a/docs/common-patterns.rst
+++ b/docs/common-patterns.rst
@@ -28,7 +28,7 @@ become the new richest.
::
- pragma solidity >0.4.99 <0.6.0;
+ pragma solidity ^0.5.0;
contract WithdrawalContract {
address public richest;
@@ -65,7 +65,7 @@ This is as opposed to the more intuitive sending pattern:
::
- pragma solidity >0.4.99 <0.6.0;
+ pragma solidity ^0.5.0;
contract SendContract {
address payable public richest;
diff --git a/docs/contracts.rst b/docs/contracts.rst
index 746f6e00..24477a62 100644
--- a/docs/contracts.rst
+++ b/docs/contracts.rst
@@ -343,7 +343,7 @@ inheritable properties of contracts and may be overridden by derived contracts.
::
- pragma solidity >0.4.99 <0.6.0;
+ pragma solidity ^0.5.0;
contract owned {
constructor() public { owner = msg.sender; }
@@ -619,7 +619,7 @@ The following statements are considered modifying the state:
::
- pragma solidity >0.4.99 <0.6.0;
+ pragma solidity ^0.5.0;
contract C {
function f(uint a, uint b) public view returns (uint) {
@@ -664,7 +664,7 @@ In addition to the list of state modifying statements explained above, the follo
::
- pragma solidity >0.4.99 <0.6.0;
+ pragma solidity ^0.5.0;
contract C {
function f(uint a, uint b) public pure returns (uint) {
@@ -758,7 +758,7 @@ Like any function, the fallback function can execute complex operations as long
::
- pragma solidity >0.4.99 <0.6.0;
+ pragma solidity ^0.5.0;
contract Test {
// This function is called for all messages sent to
@@ -1063,7 +1063,7 @@ Details are given in the following example.
::
- pragma solidity >0.4.99 <0.6.0;
+ pragma solidity ^0.5.0;
contract owned {
constructor() public { owner = msg.sender; }
@@ -1228,7 +1228,7 @@ equivalent to ``constructor() public {}``. For example:
::
- pragma solidity >0.4.99 <0.6.0;
+ pragma solidity ^0.5.0;
contract A {
uint public a;
@@ -1407,7 +1407,7 @@ Interfaces are denoted by their own keyword:
::
- pragma solidity >=0.5.0 <0.6.0;
+ pragma solidity ^0.5.0;
interface Token {
enum TokenType { Fungible, NonFungible }
diff --git a/docs/control-structures.rst b/docs/control-structures.rst
index f8016806..f32e7879 100644
--- a/docs/control-structures.rst
+++ b/docs/control-structures.rst
@@ -168,7 +168,7 @@ is compiled so recursive creation-dependencies are not possible.
::
- pragma solidity >0.4.99 <0.6.0;
+ pragma solidity ^0.5.0;
contract D {
uint public x;
@@ -291,7 +291,7 @@ the two variables have the same name but disjoint scopes.
::
- pragma solidity >0.4.99 <0.6.0;
+ pragma solidity ^0.5.0;
contract C {
function minimalScoping() pure public {
{
@@ -312,7 +312,7 @@ In any case, you will get a warning about the outer variable being shadowed.
::
- pragma solidity >0.4.99 <0.6.0;
+ pragma solidity ^0.5.0;
// This will report a warning
contract C {
function f() pure public returns (uint) {
@@ -332,7 +332,7 @@ In any case, you will get a warning about the outer variable being shadowed.
::
- pragma solidity >0.4.99 <0.6.0;
+ pragma solidity ^0.5.0;
// This will not compile
contract C {
function f() pure public returns (uint) {
@@ -379,7 +379,7 @@ a message string for ``require``, but not for ``assert``.
::
- pragma solidity >0.4.99 <0.6.0;
+ pragma solidity ^0.5.0;
contract Sharer {
function sendHalf(address payable addr) public payable returns (uint balance) {
@@ -425,7 +425,7 @@ The following example shows how an error string can be used together with revert
::
- pragma solidity >0.4.99 <0.6.0;
+ pragma solidity ^0.5.0;
contract VendingMachine {
function buy(uint amount) public payable {
diff --git a/docs/frequently-asked-questions.rst b/docs/frequently-asked-questions.rst
index ae25b935..2cc082b4 100644
--- a/docs/frequently-asked-questions.rst
+++ b/docs/frequently-asked-questions.rst
@@ -120,7 +120,7 @@ In the case of a ``contract A`` calling a new instance of ``contract B``, parent
You will need to make sure that you have both contracts aware of each other's presence and that ``contract B`` has a ``payable`` constructor.
In this example::
- pragma solidity >0.4.99 <0.6.0;
+ pragma solidity ^0.5.0;
contract B {
constructor() public payable {}
diff --git a/docs/introduction-to-smart-contracts.rst b/docs/introduction-to-smart-contracts.rst
index 7daae06a..0cce690b 100644
--- a/docs/introduction-to-smart-contracts.rst
+++ b/docs/introduction-to-smart-contracts.rst
@@ -81,7 +81,7 @@ registering with username and password — all you need is an Ethereum keypair.
::
- pragma solidity >0.4.99 <0.6.0;
+ pragma solidity ^0.5.0;
contract Coin {
// The keyword "public" makes those variables
diff --git a/docs/security-considerations.rst b/docs/security-considerations.rst
index bd06276b..d83302a0 100644
--- a/docs/security-considerations.rst
+++ b/docs/security-considerations.rst
@@ -183,7 +183,7 @@ Never use tx.origin for authorization. Let's say you have a wallet contract like
::
- pragma solidity >0.4.99 <0.6.0;
+ pragma solidity ^0.5.0;
// THIS CONTRACT CONTAINS A BUG - DO NOT USE
contract TxUserWallet {
@@ -203,7 +203,7 @@ Now someone tricks you into sending ether to the address of this attack wallet:
::
- pragma solidity >0.4.99 <0.6.0;
+ pragma solidity ^0.5.0;
interface TxUserWallet {
function transferTo(address payable dest, uint amount) external;