scrypt-inc / specification

Specification for the sCrypt Smart Contract Language

How to pull/push to transifex

• install nodejs
• install python pip
• sudo pip3 install -U transifex-client
• sudo pip3 install -U sphinx
• sudo pip3 install -U pygments-lexer-solidity
• sudo pip3 install -U sphinx_rtd_theme
• go to get a new api token
• cd docs
• npm run pull:all
• input api token:

specification's Issues

Structure refactor

Current doc structure seems a little confusing, needs some refactor.

Is the function keyword necessary?

Contracts methods are defined using the pattern "public function name()". Is the function keyword necessary? To me the function keyword seems redundant as the lexer should be able to identity that its a function by the "name()" pattern. This would reduce typing by eliminating this noise. Unless there are different function types, it would seem that this would reduce the extra typing.

怎么看不见中文文档呢?

怎么看不见中文文档呢?

pay-to-public-key-hash example

Would you add some background to this example? What does it do and what are the use cases?

https://scryptdoc.readthedocs.io/en/latest/p2pkh.html#pay-to-public-key-hash

update array writing cn

now we have en version
687b823

Issue-from-IDE: Start Debugger

• IdeVersion: 1.15.2
• Compiler Version: 1.16.0 commit.b486350
• OS platform: darwin
• OS release: 21.4.0
• Error: Cannot create a string longer than 0x1fffffe8 characters

small typo

together

需要一个中文版说明和编译器代码开源

目前已经好强大了

@state restriction in cn

715ee8d