aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorchriseth <chris@ethereum.org>2018-01-05 00:19:45 +0800
committerGitHub <noreply@github.com>2018-01-05 00:19:45 +0800
commit6a9a4e2bb860e7e1c8bd832b251dc6877912c233 (patch)
treead7dd75d3fa9513106755a0aec4131427746cb71
parentb195486501b95854603b3404f454e6333a75b765 (diff)
downloaddexon-solidity-6a9a4e2bb860e7e1c8bd832b251dc6877912c233.tar.gz
dexon-solidity-6a9a4e2bb860e7e1c8bd832b251dc6877912c233.tar.zst
dexon-solidity-6a9a4e2bb860e7e1c8bd832b251dc6877912c233.zip
Explain the difference to inline assembly.
-rw-r--r--docs/julia.rst7
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/julia.rst b/docs/julia.rst
index 309e6b36..9e961a9d 100644
--- a/docs/julia.rst
+++ b/docs/julia.rst
@@ -14,6 +14,13 @@ It can already be used for "inline assembly" inside Solidity and
future versions of the Solidity compiler will even use JULIA as intermediate
language. It should also be easy to build high-level optimizer stages for JULIA.
+.. note::
+
+ Note that the flavour used for "inline assembly" does not have types
+ (everything is ``u256``) and the built-in functions are identical
+ to the EVM opcodes. Please resort to the inline assembly documentation
+ for details.
+
The core components of JULIA are functions, blocks, variables, literals,
for-loops, if-statements, switch-statements, expressions and assignments to variables.