| Version 4 (modified by walt, 2 years ago) |
|---|
OrangeFS Development Team Developer Guidelines
OrangeFS Development Team
May 10, 2011
Introduction
This document is intended to serve as an introduction and set of guidelines for programming style and development tools that are commonly used in the Parallel Architecture Research Lab at Clemson University. We do not claim that this is the best or only way to effectively structure code or use development tools. However, adhering to these guidelines should assist in the maintenance, debugging, and documentation of code that must be consistent over the lifetime of a large software engineering project. Most of this documentation was motivated by the PVFS project, but hopefully it is applicable to other projects as well.
The coding manual is intended for use by anyone who will be regularly contributing development effort to software projects within the Parallel Architecture Research Lab.
The first portion of this document provides a brief introduction to some of the most common development tools used in the lab. All of these tools are available on the lab workstations. They are also available on most other UNIX-like platforms.
The second portion of this document covers formatting and writing standard C code. Some of these guidelines are provided to maintain consistency in the appearance of the code, while others actually assist in writing correct code or making reasonable design decisions while coding. The third section provides the Java counterpart to these guidelines.
The final section contains information that is very specific to PVFS and may not be applicable to other projects.
- Editors
- CVS
- Compiler Flags
- Debugging
- Makefiles
- Electric Fence?
- C Programming
- Documentation with Doxygen
- Specific PVFS Issues
