Updated NEP 1 : Style Guide for Nimrod Code (markdown)
This commit is contained in:
parent
ce9ae0c3e1
commit
288234c3c1
|
@ -1,9 +1,4 @@
|
||||||
Nimrod Enhancement Proposal #1 - Standard Library Style Guide
|
Nimrod Enhancement Proposal #1 - Standard Library Style Guide
|
||||||
<style>
|
|
||||||
li {
|
|
||||||
margin-bottom: 10cm;
|
|
||||||
}
|
|
||||||
</style>
|
|
||||||
|
|
||||||
Abstract
|
Abstract
|
||||||
========
|
========
|
||||||
|
@ -26,7 +21,7 @@ Spacing and Whitespace Conventions
|
||||||
- Lines should be no longer than 80 characters. Limiting the amount of
|
- Lines should be no longer than 80 characters. Limiting the amount of
|
||||||
information present on each line makes for more readable code - the reader
|
information present on each line makes for more readable code - the reader
|
||||||
has smaller chunks to process.
|
has smaller chunks to process.
|
||||||
|
<br>
|
||||||
- 2 spaces should be used for indentation of blocks; tabstops are not allowed
|
- 2 spaces should be used for indentation of blocks; tabstops are not allowed
|
||||||
(the compiler enforces this). Using spaces means that the appearance of
|
(the compiler enforces this). Using spaces means that the appearance of
|
||||||
code is more consistant across editors. Unlike spaces, tabstop width varies
|
code is more consistant across editors. Unlike spaces, tabstop width varies
|
||||||
|
|
Loading…
Reference in New Issue