Difference between revisions of "Talk:Lua code style guidelines"
Jump to navigation
Jump to search
ShadowNinja (talk | contribs) (Add comments by sapier) |
|||
Line 5: | Line 5: | ||
:* Why are spaces around equals signs in short tables allowed to be omitted? They help readability. | :* Why are spaces around equals signs in short tables allowed to be omitted? They help readability. | ||
:* I think parenthesis almost always improve readability. Why minimize the amount of them that you use? | :* I think parenthesis almost always improve readability. Why minimize the amount of them that you use? | ||
− | :-- [[User:Sapier|Sapier]] | + | :-- [[User:Sapier|Sapier]] |
+ | |||
+ | |||
+ | Forgotten comments | ||
+ | :* Don't define unspecific must rules but declare them to be suggestions | ||
+ | :* Don't forbid perfectly fine coding style as comparing against nil | ||
+ | :-- [[User:Sapier|Sapier]] |
Revision as of 20:23, 18 August 2014
Suggestions for this page:
- Multi-line comment style should be specified.
- Why shouldn't DoxyGen be used?
- I like to use something more visual like a line of dashes to separate top-level functions.
- Why are spaces around equals signs in short tables allowed to be omitted? They help readability.
- I think parenthesis almost always improve readability. Why minimize the amount of them that you use?
- -- Sapier
Forgotten comments
- Don't define unspecific must rules but declare them to be suggestions
- Don't forbid perfectly fine coding style as comparing against nil
- -- Sapier