Coding Guidelines: Difference between revisions
Jump to navigation
Jump to search
(remove localization) |
(Prettify the links) |
||
(17 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
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. | 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 Style]] | |||
* [[Coding Guidelines/Asynchronous Programming | Asynchronous Programming]] (event-based programming) | |||
* [[Coding Guidelines/Command-line Processing | Command-line Processing]] | |||
* [[Coding Guidelines/Compiler Features | Compiler Features]] | |||
* [[Coding Guidelines/Configuration | Configuration]] | |||
* [[Coding Guidelines/Debugging Functions | Debugging Functions]] | |||
* [[Coding Guidelines/Error Handling | Error Handling]] | |||
* [[Coding Guidelines/File Locking | File Locking]] | |||
* [[Coding Guidelines/Filesystem Manipulation | Filesystem Manipulation]] | |||
* [[Coding Guidelines/Glib Utilities | Glib Utilities]] | |||
* [[Coding Guidelines/GValue Handling | GValue Handling]] | |||
* [[Coding Guidelines/Internationalization | Internationalization]] | |||
* [[Coding Guidelines/IPv6 Support | IPv6 Support]] | |||
* [[Coding Guidelines/Memory Allocation | Memory Allocation]] | |||
* [[Coding Guidelines/Parsing Functions | Parsing Functions]] | |||
* [[Coding Guidelines/Perl Pitfalls | Perl Pitfalls]] | |||
* [[Coding Guidelines/Quoting | Quoting]] | |||
* [[Coding Guidelines/Safely Executing Other Processes | Safely Executing Other Processes]] | |||
* [[Coding Guidelines/String Functions | String Functions]] | |||
* [[Coding Guidelines/SWIG Gotchas | 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 <tt>/</tt> (to make a [http://meta.wikimedia.org/wiki/Subpages MediaWiki subpage]), to avoid collisions with other documentation.'' | ''Editors: please link articles from this page, rather than adding content here, to allow links from other articles. Article titles should begin with <tt>/</tt> (to make a [http://meta.wikimedia.org/wiki/Subpages MediaWiki subpage]), to avoid collisions with other documentation.'' | ||
Latest revision as of 18:13, 16 December 2023
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.