|
|
<p>This wiki page contains coding guidelines that all developers must follow as standard practice in ADIOS 2.0 to take full advantage of the latest C++11 standard. This list is open as corrections and new ideas/suggestions come in place. Take them as mandatory good practices to improve ADIOS2 development and collaboration. Many topics are taken from Stroustrup, Sutter, and Meyers books, the clang-format, and google C++ style guide.
|
|
|
|
|
|
**Objectives:**
|
|
|
<h3 class=""><code>Collaboration</code></h3>
|
|
|
<ul><li>Make your work easy to understand and share</li>
|
|
|
<li>Allocate more time for path-finding, new functionality, and performance improvements rather than understanding developers' coding styles</li>
|
|
|
<li>Expand developers and users base</li></ul>
|
|
|
|
|
|
<h3 class=""><code>Execution</code></h3><ul><li>Execute new ideas faster by using features already in the language standard</li></ul>
|
|
|
<h3 class=""><code>Quality</code></h3><ul><li>Improve the quality of the final software product: reduce potential security risks (segmentation faults, memory leaks and overflows)</li></ul>
|
|
|
</p> |
|
|
\ No newline at end of file |