From ccb7fd5c2b536ee1002fbf91f8584cd0d08c7c06 Mon Sep 17 00:00:00 2001 From: sorin-ionescu Date: Tue, 28 Jun 2011 09:16:38 -0700 Subject: [PATCH] Functions are easier to spot with the optional 'function' keyword since curly braces can be used to create a list of commands to be executed in the current context. --- Coding-style-guide.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/Coding-style-guide.md b/Coding-style-guide.md index 9559b01..45ea5c1 100644 --- a/Coding-style-guide.md +++ b/Coding-style-guide.md @@ -1,4 +1,3 @@ - ## Variables Meaningful self documenting names should be used, if the variable name does not make it reasonably obvious as to the meaning, appropriate comments should be added. @@ -14,13 +13,13 @@ Variables name should not clobber command names, such as `dir`, `pwd` Braces should be on the same line as the function name: - helpful() { + function helpful() { ... } Private or utility functions should be prefixed with an underscore: - _helper_util() { + function _helper_util() { ... }