Coding Guidelines
This article summarizes the "things every developer should know". This will never be an exhaustive list, but it provides a convenient, common place to share the many guidelines and suggestions that each developer has in his or her head.
See also DEVELOPING in the top-level source directory.
- Coding Guidelines/Coding Style
- Coding Guidelines/Asynchronous Programming (event-based programming)
- Coding Guidelines/Command-line Processing
- Coding Guidelines/Compiler Features
- Coding Guidelines/Configuration
- Coding Guidelines/Debugging Functions
- Coding Guidelines/Error Handling
- Coding Guidelines/File Locking
- Coding Guidelines/Filesystem Manipulation
- Coding Guidelines/Glib Utilities
- Coding Guidelines/GValue Handling
- Coding Guidelines/Internationalization
- Coding Guidelines/IPv6 Support
- Coding Guidelines/Memory Allocation
- Coding Guidelines/Parsing Functions
- Coding Guidelines/Perl Pitfalls
- Coding Guidelines/Quoting
- Coding Guidelines/Safely Executing Other Processes
- Coding Guidelines/String Functions
- Coding Guidelines/SWIG Gotchas
Also see:
- Perl Interface for an overview of Amanda's perl modules
- Testing to see how Amanda's testing architecture can help you
Editors: please link articles from this page, rather than adding content here, to allow links from other articles. Article titles should begin with / (to make a MediaWiki subpage), to avoid collisions with other documentation.