Coding style guide

Joshua McKinney edited this page 2016-09-11 16:21:54 -05:00

Wiki Page Revisions

16 Commits

Author	SHA1	Message	Date
Joshua McKinney	68759b6fe7	Fix link to google shell style guide in coding style doc	2016-09-11 16:21:54 -05:00
Lars Moelleken	8dcbb407a0	Drops the `function` keyword and uses only `func(){}` syntax as per the POSIX specification: v2	2015-11-06 13:45:12 +01:00
Lars Moelleken	fed196a67d	Drops the `function` keyword and uses only `func(){}` syntax as per the POSIX specification: http://pubs.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#tag_02_09_05	2015-11-06 13:41:50 +01:00
Khas'Mek	1c890e4af9	Consistency in design and formatting update.	2015-05-31 08:24:16 -04:00
Andrew Janke	1cd6f5ce15	Minor markup formatting change	2015-05-29 22:39:50 -04:00
Andrew Janke	55534bc2eb	Require explicit "function" keyword in function definitions	2015-05-29 22:27:06 -04:00
Andrew Janke	a215b02413	Fix code formatting, a bit of typography	2015-03-29 19:56:33 -04:00
Lars Moelleken	d125670722	adding some code-examples (need review!)	2015-03-30 01:20:28 +02:00
Lars Moelleken	c5bdb612c1	adding some code-guidelines ...	2015-03-01 23:50:33 +01:00
CoolOppo	19a8329bfe	Formatted with markdownfmt	2014-10-04 12:26:40 -07:00
sunaku	e5a7bbe845	add syntax highlighting to code blocks	2011-06-28 14:28:39 -07:00
sunaku	6d64481bb8	markdown removed the [[ in the if-statement	2011-06-28 14:27:13 -07:00
sorin-ionescu	c7670fb339	ZSH uses dash instead of underscore to separate words in function identifiers.	2011-06-28 14:06:19 -07:00
sorin-ionescu	ccb7fd5c2b	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.	2011-06-28 09:16:38 -07:00
csexton	5ee61cef2f	First hack at a little structure.	2011-06-28 08:57:20 -07:00
robbyrussell	94552ecf03	Created Coding style guide (markdown)	2011-06-01 14:45:10 -07:00