zzh
/
gatk-3.8
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

This document is now up as content on the wiki, so I'm removing it from svn. 

git-svn-id: file:///humgen/gsa-scr1/gsa-engineering/svn_contents/trunk@1140 348d0f76-0448-11de-a6fe-93d51630548a
This commit is contained in:
aaron 2009-07-01 15:40:32 +00:00
parent d58eeb7539
commit 05c5659053
2 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
doc/GATK_Coding_Standards.pdf
View File

Binary file not shown.

2
doc/GATK_Coding_Standards.tex
View File

@ -17,7 +17,7 @@ informatics team here at the Broad Institute. They deserve all the credit for t
of gratitude with them.
\section{Summary}
This document is an attempt to describe a brief and minimal set of standards for Java code for use by production informatics projects at the Broad. The goal of the standards is to allow programmers to be innovative and expressive, while allowing their peers a vague hope of maintaining and extending their output. This document describes a set of arbitrary standards for naming and documentation based on industry-standard practices, and a set of Ògood practicesÓ guidelines intended to improve the maintainability, correctness, and reusability of code. Good citizenship demands that you suggest improvements if you feel that the document is not well crafted, rather than merely going your own way
This document is an attempt to describe a brief and minimal set of standards for Java code for use by production informatics projects at the Broad. The goal of the standards is to allow programmers to be innovative and expressive, while allowing their peers a vague hope of maintaining and extending their output. This document describes a set of arbitrary standards for naming and documentation based on industry-standard practices, and a set of Ògood practicesÓ guidelines intended to improve the maintainability, correctness, and reusability of code. Good citizenship demands that you suggest improvements if you feel that the document is not well crafted, rather than merely going your own way.
\pagebreak
\section{Cheat Sheet}
\begin{table}[htdp]