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

[DOCS] Some more explanation about pragmas.

Browse Source
This commit is contained in:
chriseth 2018-09-25 20:03:53 +02:00
parent b08d49338e
commit 3cec3f13e5
1 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/layout-of-source-files.rst
View File

@ -13,6 +13,12 @@ and :ref:`pragma directives<pragma>`.
Pragmas Pragmas
======= =======
The ``pragma`` keyword can be used to enable certain compiler features
or checks. A pragma directive is always local to a source file, so
you have to add the pragma to all your files if you want enable it
in all of your project. If you :ref:`import<import>` another file, the pragma
from that file will not automatically apply to the importing file.
.. index:: ! pragma, version .. index:: ! pragma, version
.. _version_pragma: .. _version_pragma:
@ -43,6 +49,13 @@ the exact version of the compiler, so that bugfix releases are still possible.
It is possible to specify much more complex rules for the compiler version, It is possible to specify much more complex rules for the compiler version,
the expression follows those used by `npm <https://docs.npmjs.com/misc/semver>`_. the expression follows those used by `npm <https://docs.npmjs.com/misc/semver>`_.
.. note::
Using the version pragma will *not* change the version of the compiler.
It will also *not* enable or disable features of the compiler. It will just
instruct the compiler to check whether its version matches the one
required by the pragma. If it does not match, the compiler will issue
an error.
.. index:: ! pragma, experimental .. index:: ! pragma, experimental
.. _experimental_pragma: .. _experimental_pragma: