Changes between Version 30 and Version 31 of Commentary/CodingStyle


Ignore:
Timestamp:
Apr 24, 2011 9:54:13 PM (3 years ago)
Author:
megacz
Comment:

link to WorkingConventions

Legend:

Unmodified
Added
Removed
Modified
  • Commentary/CodingStyle

    v30 v31  
    44 = The GHC Commentary - Coding Style Guidelines for the compiler =  
    55 
    6 This is a rough description of some of the coding practices and style that we use for Haskell code inside {{{compiler}}}.  (For run-time system code see the [wiki:Commentary/Rts/Conventions Coding Style Guidelines for RTS C code].) 
     6This is a rough description of some of the coding practices and style that we use for Haskell code inside {{{compiler}}}.  For run-time system code see the [wiki:Commentary/Rts/Conventions Coding Style Guidelines for RTS C code].  Also see the wiki page on [wiki:WorkingConventions Working Conventions] for issues related to version control, workflow, testing, bug tracking and other miscellany. 
    77 
    88The general rule is to stick to the same coding style as is already used in the file you're editing. If you must make stylistic changes, commit them separately from functional changes, so that someone looking back through the change logs can easily distinguish them.