diff options
| author | Henrik Hodne <dvyjones@binaryhex.com> | 2012-01-26 21:31:57 +0400 |
|---|---|---|
| committer | isaacs <i@izs.me> | 2012-02-29 06:57:47 +0400 |
| commit | f5321db1dd9ec0a18623fe5f2b3f524f2c6ee103 (patch) | |
| tree | 3c8e99241835fc999c1d5ddabd908f9c3fb7338e | |
| parent | 4d59f325d1b5f88ed6a842316fa7f68a8b311ebe (diff) | |
Add "`"s for code.
| -rw-r--r-- | doc/cli/coding-style.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/cli/coding-style.md b/doc/cli/coding-style.md index 5315c575c..42ac1d785 100644 --- a/doc/cli/coding-style.md +++ b/doc/cli/coding-style.md @@ -59,8 +59,8 @@ Don't use them except in four situations: * `for (;;)` loops. They're actually required. * null loops like: `while (something) ;` (But you'd better have a good reason for doing that.) -* case "foo": doSomething(); break -* In front of a leading ( or [ at the start of the line. +* `case "foo": doSomething(); break` +* In front of a leading `(` or `[` at the start of the line. This prevents the expression from being interpreted as a function call or property access, respectively. |