From c416256f1564ba1568d3954ff45dd826ad79320f Mon Sep 17 00:00:00 2001 From: Dominik Picheta Date: Mon, 28 Apr 2014 13:19:37 -0700 Subject: [PATCH] Updated Nimrod Enhancement Proposal #1 (markdown) --- Nimrod-Enhancement-Proposal-#1.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Nimrod-Enhancement-Proposal-#1.md b/Nimrod-Enhancement-Proposal-#1.md index fa56b6a..0da3591 100644 --- a/Nimrod-Enhancement-Proposal-#1.md +++ b/Nimrod-Enhancement-Proposal-#1.md @@ -10,7 +10,7 @@ proposal aims to list a series of guidelines that the standard library should follow. Note that these are *guidelines* only. The nature of Nimrod being as flexible as it is, there will be parts of this style guide that don't make sense in certain contexts. Furthermore, just as -(Python's style guide)[http://legacy.python.org/dev/peps/pep-0008/] changes +[Python's style guide](http://legacy.python.org/dev/peps/pep-0008/) changes over time, this style guide will too. Style Guidelines @@ -19,12 +19,12 @@ Style Guidelines General ------- - All identifiers, except for types, should be in pascalCase. Type identifiers - Should be in CamelCase. + should be in CamelCase. - Members of enums should have an identifying prefix before their names. For example, the PathComponent enum in the os module contains the pcFile member, which, like the other members, has the 'pc' - (standing for PathComponent) prefix before its name. + (standing for PathComponent) prefix before its name. An exception to this rule exists when using ``pure`` enums. - Lines should be no longer than 80 characters