workflow: document current C++ approach

Signed-off-by: David Lamparter <equinox@diac24.net>

diff --git a/doc/developer/workflow.rst b/doc/developer/workflow.rst
index 6e426afeb57b0fe2848b4bc15dd6c5e0b2abd130..07c43ac2de7054fae1259fe5634834754450c2a2 100644 (file)
--- a/doc/developer/workflow.rst
+++ b/doc/developer/workflow.rst
@@ -368,6 +368,19 @@ Documentation should be written in reStructuredText. Sphinx extensions may be
 utilized but pure ReST is preferred where possible. See
 :ref:`documentation`.
 
+Use of C++
+----------
+
+While C++ is not accepted for core components of FRR, extensions, modules or
+other distinct components may want to use C++ and include FRR header files.
+There is no requirement on contributors to work to retain C++ compatibility,
+but fixes for C++ compatibility are welcome.
+
+This implies that the burden of work to keep C++ compatibility is placed with
+the people who need it, and they may provide it at their leisure to the extent
+it is useful to them.  So, if only a subset of header files, or even parts of
+a header file are made available to C++, this is perfectly fine.
+
 Code Reviews
 ============