aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorchriseth <chris@ethereum.org>2017-10-26 16:34:58 +0800
committerGitHub <noreply@github.com>2017-10-26 16:34:58 +0800
commit59d4dfbd9bf530db9260c7048423fe4c4b2870f5 (patch)
tree0f4186f5f30e4c8cbad82f27be56f572fa298c6e
parentcacc0e4b469e179b8e2ce73bf217b65ad720630c (diff)
parent58778be567620a550210150f8616440b9a5dbd55 (diff)
downloaddexon-solidity-59d4dfbd9bf530db9260c7048423fe4c4b2870f5.tar.gz
dexon-solidity-59d4dfbd9bf530db9260c7048423fe4c4b2870f5.tar.zst
dexon-solidity-59d4dfbd9bf530db9260c7048423fe4c4b2870f5.zip
Merge pull request #3130 from nakov/patch-1
Improved the "Naming" section
-rw-r--r--docs/style-guide.rst34
1 files changed, 18 insertions, 16 deletions
diff --git a/docs/style-guide.rst b/docs/style-guide.rst
index 0742d2e9..66fae0c4 100644
--- a/docs/style-guide.rst
+++ b/docs/style-guide.rst
@@ -696,49 +696,51 @@ indistinguishable from the numerals one and zero.
Contract and Library Names
==========================
-Contracts and libraries should be named using the CapWords style.
+Contracts and libraries should be named using the CapWords style. Examples: ``SimpleToken``, ``SmartBank``, ``CertificateHashRepository``, ``Player``.
-Events
-======
+Event Names
+===========
-Events should be named using the CapWords style.
+Events should be named using the CapWords style. Examples: ``Deposit``, ``Transfer``, ``Approval``, ``BeforeTransfer``, ``AfterTransfer``.
Function Names
==============
-Functions should use mixedCase.
+Functions should use mixedCase. Examples: ``getBalance``, ``transfer``, ``verifyOwner``, ``addMember``, ``changeOwner``.
-Function Arguments
-==================
+Function Argument Names
+=======================
+
+Function arguments should use mixedCase. Examples: ``initialSupply``, ``account``, ``recipientAddress``, ``senderAddress``, ``newOwner``.
When writing library functions that operate on a custom struct, the struct
should be the first argument and should always be named ``self``.
-Local and State Variables
-=========================
+Local and State Variable Names
+==============================
-Use mixedCase.
+Use mixedCase. Examples: ``totalSupply``, ``remainingSupply``, ``balancesOf``, ``creatorAddress``, ``isPreSale``, ``tokenExchangeRate``.
Constants
=========
Constants should be named with all capital letters with underscores separating
-words. (for example:``MAX_BLOCKS``)
+words. Examples: ``MAX_BLOCKS``, `TOKEN_NAME`, ``TOKEN_TICKER``, ``CONTRACT_VERSION``.
-Modifiers
-=========
+Modifier Names
+==============
-Use mixedCase.
+Use mixedCase. Examples: ``onlyBy``, ``onlyAfter``, ``onlyDuringThePreSale``.
-Avoiding Collisions
-===================
+Avoiding Naming Collisions
+==========================
* ``single_trailing_underscore_``