From dc345cf7fdbfec32602a2febcb884c93ce58cd02 Mon Sep 17 00:00:00 2001 From: Sebastian Huber Date: Thu, 5 Nov 2020 19:38:12 +0100 Subject: eng: Clarify "Source Documentation" section --- eng/coding-conventions.rst | 27 +++++++++++++++++---------- 1 file changed, 17 insertions(+), 10 deletions(-) (limited to 'eng/coding-conventions.rst') diff --git a/eng/coding-conventions.rst b/eng/coding-conventions.rst index e7a67ec..5dd8df5 100644 --- a/eng/coding-conventions.rst +++ b/eng/coding-conventions.rst @@ -18,17 +18,24 @@ for examples that illustrate style rules and Doxygen usage. Source Documentation -------------------- -* Use Doxygen according to our `Doxygen Recommendations `_.. -* Start each file with a brief description followed by a license. - See `Boilerplate File Header `_.. +* Use Doxygen according to our :ref:`DoxygenGuidelines`. + +* Use the file templates, see :ref:`FileTemplates`. + * Use ``/* */`` comments. -* Use comments wisely within function bodies, to explain - or draw attention without being verbose. -* Use English prose and strive for good grammar, - spelling, and punctuation. -* Use TODO: with a comment to indicate code that needs improvement. - Make it clear what there is to do. -* Use XXX or FIXME to indicate an error/bug/broken code. + +* Do not use ``//`` comments. + +* Use comments wisely within function bodies, to explain or draw attention + without being verbose. + +* Use English prose and strive for good grammar, spelling, and punctuation. + +* Use ``TODO`` with a comment to indicate code that needs improvement. Make + it clear what there is to do. Add a ticket and add a link to it. + +* Use ``XXX`` or ``FIXME`` to indicate an error/bug/broken code. Add a ticket + and add a link to it. Licenses -------- -- cgit v1.2.3