Coding Guidelines
Jump to navigation
Jump to search
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 Style
- Asynchronous Programming (event-based programming)
- Command-line Processing
- Compiler Features
- Configuration
- Debugging Functions
- Error Handling
- File Locking
- Filesystem Manipulation
- Glib Utilities
- GValue Handling
- Internationalization
- IPv6 Support
- Memory Allocation
- Parsing Functions
- Perl Pitfalls
- Quoting
- Safely Executing Other Processes
- String Functions
- 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.