From 63bc2441630a431cc1715c57f6ffdc0471e0dd2b Mon Sep 17 00:00:00 2001 From: Anthony De Meulemeester Date: Sat, 24 Feb 2018 10:19:15 +0100 Subject: [PATCH] Updated readme in compiler folder + bumped version to match latest tag. (#29) * Updated readme in compiler folder + bumped version to match latest tag. --- VERSION | 2 +- pkg/vm/compiler/README.md | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/VERSION b/VERSION index 54d1a4f2a..a55105169 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -0.13.0 +0.15.0 diff --git a/pkg/vm/compiler/README.md b/pkg/vm/compiler/README.md index 43d3918dc..f3c495243 100644 --- a/pkg/vm/compiler/README.md +++ b/pkg/vm/compiler/README.md @@ -50,20 +50,20 @@ Due to the limitations of the NEO virtual machine, features listed below will no ### Compile a smart contract ``` -./bin/neo-go contract compile mycontract.go +./bin/neo-go contract compile -i mycontract.go ``` By default the filename will be the name of your .go file with the .avm extension, the file will be located in the same directory where you called the command from. If you want another location for your compiled contract: ``` -./bin/neo-go contract compile mycontract.go --out /Users/foo/bar/contract.avm +./bin/neo-go contract compile -i mycontract.go --out /Users/foo/bar/contract.avm ``` ### Debugging your smart contract You can dump the opcodes generated by the compiler with the following command: ``` -./bin/neo-go contract opdump mycontract.go +./bin/neo-go contract opdump -i mycontract.go ``` This will result in something like this: @@ -81,4 +81,4 @@ INDEX OPCODE DESC 8 0x52 OpPush2 9 0x7a OpRoll 10 0xc4 OpSetItem -``` \ No newline at end of file +```