Coding Guidelines: Difference between revisions
Jump to navigation
Jump to search
(new link) |
(new page on quoting) |
||
| Line 18: | Line 18: | ||
* [[/Memory Allocation]] | * [[/Memory Allocation]] | ||
* [[/Parsing Functions]] | * [[/Parsing Functions]] | ||
* [[/Quoting]] | |||
* [[/Safely Executing Other Processes]] | * [[/Safely Executing Other Processes]] | ||
* [[/String Functions]] | * [[/String Functions]] | ||
Revision as of 22:14, 3 February 2009
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
- /Quoting
- /Safely Executing Other Processes
- /String Functions
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.