diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/index.rst | 2 | ||||
| -rw-r--r-- | docs/layout-of-source-files.rst | 8 |
2 files changed, 6 insertions, 4 deletions
diff --git a/docs/index.rst b/docs/index.rst index ed931163..16745c07 100644 --- a/docs/index.rst +++ b/docs/index.rst @@ -19,6 +19,8 @@ user-defined types among other features. With Solidity you can create contracts for uses such as voting, crowdfunding, blind auctions, and multi-signature wallets. +When deploying contracts, you should use the latest released version of Solidity. This is because breaking changes as well as new features and bug fixes are introduced regularly. We currently use a 0.x version number [to indicate this fast pace of change](https://semver.org/#spec-item-4). + Language Documentation ---------------------- diff --git a/docs/layout-of-source-files.rst b/docs/layout-of-source-files.rst index fa36fc6a..235f4dd4 100644 --- a/docs/layout-of-source-files.rst +++ b/docs/layout-of-source-files.rst @@ -37,12 +37,12 @@ breaking changes, those releases will always have versions of the form The version pragma is used as follows:: - pragma solidity ^0.4.0; + pragma solidity ^0.5.2; -Such a source file will not compile with a compiler earlier than version 0.4.0 -and it will also not work on a compiler starting from version 0.5.0 (this +Such a source file will not compile with a compiler earlier than version 0.5.2 +and it will also not work on a compiler starting from version 0.6.0 (this second condition is added by using ``^``). The idea behind this is that -there will be no breaking changes until version ``0.5.0``, so we can always +there will be no breaking changes until version ``0.6.0``, so we can always be sure that our code will compile the way we intended it to. We do not fix the exact version of the compiler, so that bugfix releases are still possible. |