From c7dc46faef3c3e402e6ecf78332e8d80a4939729 Mon Sep 17 00:00:00 2001 From: Wolfgang Bangerth Date: Thu, 12 Sep 2024 12:56:42 -0600 Subject: [PATCH] Remove a section about ways to use doxygen that we don't use. --- doc/developers/writing-documentation.html | 20 -------------------- 1 file changed, 20 deletions(-) diff --git a/doc/developers/writing-documentation.html b/doc/developers/writing-documentation.html index 83d9df1cc6..40d4777c16 100644 --- a/doc/developers/writing-documentation.html +++ b/doc/developers/writing-documentation.html @@ -238,26 +238,6 @@ void foobar () -

Code examples for the usage of single classes

-

- Writing example files for classes is supported by - doxygen. These example files go into - deal.II/examples/doxygen. If they are short, - documentation should be inside and they are included into the - documentation with @include filename. Take a look how - the class BlockMatrixArray does this. -

- -

- Larger example files should be documented using the - doxygen command @dotinclude and - related commands. However, if these programs do something - reasonable and do not only demonstrate a single topic, you should - consider converting them to a complete example program in the - step-XX series. -

- -

Writing example programs for the tutorial

-- 2.39.5