summaryrefslogtreecommitdiffstatshomepage
diff options
context:
space:
mode:
author balr0g <balrog032@gmail.com>2015-05-18 09:51:17 -0400
committer balr0g <balrog032@gmail.com>2015-05-18 10:46:14 -0400
commit71bac92863d752e5186cd02f1fb65ca29f4c5208 (patch)
tree3691abba785ca91e400787f26e128f38f5bfe948
parent12b316879ced572776f0269631da2c892d1f197c (diff)
Minor changes for clarity (nw)
-rw-r--r--README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/README.md b/README.md
index b4028e0c49e..843027a7e99 100644
--- a/README.md
+++ b/README.md
@@ -55,6 +55,6 @@ Contributing
## Coding standard
-MAME source code should be viewed and edited with your editor set to use four spaces per tab. Tabs are used for initial indentation of lines, with one tab used per indentation level. Spaces are used for other alignment within a line.
+MAME source code should be viewed and edited with your editor set to use four spaces per tab. Tabs are used for initial indentation of lines, with one tab used per indentation level. Spaces are used for other alignment within a line.
-Some parts of the code follow GNU style, some parts of the code follow K&R style, mostly depending on who wrote the original version. Above all else, be consistent with what you modify. For new code, the majority tends to prefer GNU style, so if you don't care much, use that.
+Some parts of the code follow [GNU style](http://www.gnu.org/prep/standards/html_node/Formatting.html); some parts of the code follow [K&R style](https://en.wikipedia.org/wiki/Indent_style#K.26R_style) -- mostly depending on who wrote the original version. **Above all else, be consistent with what you modify, and keep whitespace changes to a minimum when modifying existing source.** For new code, the majority tends to prefer GNU style, so if you don't care much, use that.