{"id":2218971,"url":"http://patchwork.ozlabs.org/api/patches/2218971/?format=json","web_url":"http://patchwork.ozlabs.org/project/gcc/patch/20260402074533.905171-1-jwakely@redhat.com/","project":{"id":17,"url":"http://patchwork.ozlabs.org/api/projects/17/?format=json","name":"GNU Compiler Collection","link_name":"gcc","list_id":"gcc-patches.gcc.gnu.org","list_email":"gcc-patches@gcc.gnu.org","web_url":null,"scm_url":null,"webscm_url":null,"list_archive_url":"","list_archive_url_format":"","commit_url_format":""},"msgid":"<20260402074533.905171-1-jwakely@redhat.com>","list_archive_url":null,"date":"2026-04-02T07:43:29","name":"[oops/10] libstdc++: Update Doxygen config to 1.17.0","commit_ref":null,"pull_url":null,"state":"new","archived":false,"hash":"a7bdb7a03e1b248ca5d38e465af6fe77382eebc1","submitter":{"id":48004,"url":"http://patchwork.ozlabs.org/api/people/48004/?format=json","name":"Jonathan Wakely","email":"jwakely@redhat.com"},"delegate":null,"mbox":"http://patchwork.ozlabs.org/project/gcc/patch/20260402074533.905171-1-jwakely@redhat.com/mbox/","series":[{"id":498446,"url":"http://patchwork.ozlabs.org/api/series/498446/?format=json","web_url":"http://patchwork.ozlabs.org/project/gcc/list/?series=498446","date":"2026-04-02T07:43:29","name":"[oops/10] libstdc++: Update Doxygen config to 1.17.0","version":1,"mbox":"http://patchwork.ozlabs.org/series/498446/mbox/"}],"comments":"http://patchwork.ozlabs.org/api/patches/2218971/comments/","check":"pending","checks":"http://patchwork.ozlabs.org/api/patches/2218971/checks/","tags":{},"related":[],"headers":{"Return-Path":"","X-Original-To":["incoming@patchwork.ozlabs.org","gcc-patches@gcc.gnu.org"],"Delivered-To":["patchwork-incoming@legolas.ozlabs.org","gcc-patches@gcc.gnu.org"],"Authentication-Results":["legolas.ozlabs.org;\n\tdkim=pass (1024-bit key;\n unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256\n header.s=mimecast20190719 header.b=IuZaihe2;\n\tdkim-atps=neutral","legolas.ozlabs.org;\n spf=pass (sender SPF authorized) smtp.mailfrom=gcc.gnu.org\n (client-ip=2620:52:6:3111::32; helo=vm01.sourceware.org;\n envelope-from=gcc-patches-bounces~incoming=patchwork.ozlabs.org@gcc.gnu.org;\n receiver=patchwork.ozlabs.org)","sourceware.org;\n\tdkim=pass (1024-bit key,\n unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256\n header.s=mimecast20190719 header.b=IuZaihe2","sourceware.org; dmarc=pass (p=quarantine dis=none)\n header.from=redhat.com","sourceware.org; spf=pass smtp.mailfrom=redhat.com","server2.sourceware.org;\n arc=none smtp.remote-ip=170.10.133.124"],"Received":["from vm01.sourceware.org (vm01.sourceware.org\n [IPv6:2620:52:6:3111::32])\n\t(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)\n\t key-exchange x25519 server-signature ECDSA (secp384r1) server-digest SHA384)\n\t(No client certificate requested)\n\tby legolas.ozlabs.org (Postfix) with ESMTPS id 4fmYq33vrWz1yFv\n\tfor ; Thu, 02 Apr 2026 18:47:27 +1100 (AEDT)","from vm01.sourceware.org (localhost [127.0.0.1])\n\tby sourceware.org (Postfix) with ESMTP id 628B54BA2E23\n\tfor ; Thu, 2 Apr 2026 07:47:25 +0000 (GMT)","from us-smtp-delivery-124.mimecast.com\n (us-smtp-delivery-124.mimecast.com [170.10.133.124])\n by sourceware.org (Postfix) with ESMTP id 393954BA23CC\n for ; Thu, 2 Apr 2026 07:45:40 +0000 (GMT)","from mx-prod-mc-08.mail-002.prod.us-west-2.aws.redhat.com\n (ec2-35-165-154-97.us-west-2.compute.amazonaws.com [35.165.154.97]) by\n relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3,\n cipher=TLS_AES_256_GCM_SHA384) id us-mta-230-q8jeU7RMPueQH5SxOQuJYA-1; Thu,\n 02 Apr 2026 03:45:38 -0400","from mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com\n (mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.12])\n (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)\n key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest\n SHA256)\n (No client certificate requested)\n by mx-prod-mc-08.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS\n id E843118002CD; Thu, 2 Apr 2026 07:45:36 +0000 (UTC)","from zen.kayari.org (unknown [10.44.32.41])\n by mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP\n id 2F7DA19560A6; Thu, 2 Apr 2026 07:45:34 +0000 (UTC)"],"DKIM-Filter":["OpenDKIM Filter v2.11.0 sourceware.org 628B54BA2E23","OpenDKIM Filter v2.11.0 sourceware.org 393954BA23CC"],"DMARC-Filter":"OpenDMARC Filter v1.4.2 sourceware.org 393954BA23CC","ARC-Filter":"OpenARC Filter v1.0.0 sourceware.org 393954BA23CC","ARC-Seal":"i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1775115940; cv=none;\n b=ZmCKJNz3lBsM/6h7YC93B9xtUJVppJVD/voAJb9Gb7R1+Hbj60lzAMsYxEFhn2oU5VIVskD9KqYj9QZJsN9s2zCmj1zEN/AXx70OF+OcIB+32Izdwn4Bfl+CmRy96z4XZ4OT0Liv/dZAUi0iGwBO3gnVJ+JGeP1ojPRi7ka1pZ0=","ARC-Message-Signature":"i=1; a=rsa-sha256; d=sourceware.org; s=key;\n t=1775115940; c=relaxed/simple;\n bh=g7a3Dc+n5P7Y0hD3vRvRIRETW9kX9nIiQRnZYHs9aTk=;\n h=DKIM-Signature:From:To:Subject:Date:Message-ID:MIME-Version;\n b=JI0kCCC+bViOb0+sWDDlFXWV3OHZQeJMlhTYHQGXxSeL9U7DY9F+U6UwEMOIxtte1GCEctpiGi9lGJfUovgilp5jMB/C5/C7NfTF7hWtZ4OLEzRXElXysNZrW4rxOm4sMWefJti/Z9gp4rwfkKrHlMEV6LXGORqdqPr6i00JygM=","ARC-Authentication-Results":"i=1; server2.sourceware.org","DKIM-Signature":"v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;\n s=mimecast20190719; t=1775115939;\n h=from:from:reply-to:subject:subject:date:date:message-id:message-id:\n to:to:cc:mime-version:mime-version:content-type:content-type:\n content-transfer-encoding:content-transfer-encoding:\n in-reply-to:in-reply-to:references:references;\n bh=PHChTiBzajWjBU/qghV+Qr62/jm5IlViWq4Jo73qRbI=;\n b=IuZaihe2oJ+cAfPFIw6TdsMZ5EkhAMQseW/baJ4/UTfaUwtd9SUqN2Tc3KdqZJDKpPLfXy\n 6xyidd+AT1BcH5wNYvnufIXthJJ3k41IFEvsH/6wn+ZNG3XDOxcMiaOIp6hwFAugzWFE53\n 9mDrz+CMcW8XLcSZyBL51U+V1Aa3W6E=","X-MC-Unique":"q8jeU7RMPueQH5SxOQuJYA-1","X-Mimecast-MFC-AGG-ID":"q8jeU7RMPueQH5SxOQuJYA_1775115937","From":"Jonathan Wakely ","To":"gcc-patches@gcc.gnu.org,\n\tlibstdc++@gcc.gnu.org","Subject":"[PATCH oops/10] libstdc++: Update Doxygen config to 1.17.0","Date":"Thu, 2 Apr 2026 08:43:29 +0100","Message-ID":"<20260402074533.905171-1-jwakely@redhat.com>","In-Reply-To":"20260401215920.674286-1-jwakely@redhat.com","References":"","MIME-Version":"1.0","X-Scanned-By":"MIMEDefang 3.0 on 10.30.177.12","X-Mimecast-Spam-Score":"0","X-Mimecast-MFC-PROC-ID":"ezFuA0c0CjSWjuIesAGH47BpNq4_hsDeO3BCcfds3ts_1775115937","X-Mimecast-Originator":"redhat.com","Content-Type":"text/plain","Content-Transfer-Encoding":"8bit","X-BeenThere":"gcc-patches@gcc.gnu.org","X-Mailman-Version":"2.1.30","Precedence":"list","List-Id":"Gcc-patches mailing list ","List-Unsubscribe":",\n ","List-Archive":"","List-Post":"","List-Help":"","List-Subscribe":",\n ","Errors-To":"gcc-patches-bounces~incoming=patchwork.ozlabs.org@gcc.gnu.org"},"content":"The changes were done automatically using 'doxygen -u' to rebase the\nconfig on Doxygen 1.17.0, which added a number of new config options and\nremoved HTML_TIMESTAMP and LATEX_TIMESTAMP.\n\nlibstdc++-v3/ChangeLog:\n\n\t* doc/doxygen/user.cfg.in: Update Doxygen config.\n---\n\nI meant to send this as the first patch in the series, but got my\ngit-send-email arguments wrong and the series started from the patch\n*after* this one.\n\nThe following comment from [PATCH 1/10] was meant to refer to this\npatch:\n\nTested x86_64-linux, with Doxygen 1.13.2 and 1.17.0 (from git)\n\nWith 1.13.2 some of the new config settings cause warnings because\nthey're not recognized:\n\nwarning: ignoring unsupported tag 'MARKDOWN_STRICT' at line 371, file /home/jwakely/src/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/doc/doxygen/html.cfg\nwarning: ignoring unsupported tag 'GENERATE_REQUIREMENTS' at line 796, file /home/jwakely/src/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/doc/doxygen/html.cfg\nwarning: ignoring unsupported tag 'REQ_TRACEABILITY_INFO' at line 810, file /home/jwakely/src/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/doc/doxygen/html.cfg\nwarning: ignoring unsupported tag 'PAGE_OUTLINE_PANEL' at line 2091, file /home/jwakely/src/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/doc/doxygen/html.cfg\nwarning: ignoring unsupported tag 'UML_MAX_EDGE_LABELS' at line 3116, file /home/jwakely/src/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/doc/doxygen/html.cfg\nwarning: ignoring unsupported tag 'MERMAID_PATH' at line 3311, file /home/jwakely/src/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/doc/doxygen/html.cfg\nwarning: ignoring unsupported tag 'MERMAID_CONFIG_FILE' at line 3317, file /home/jwakely/src/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/doc/doxygen/html.cfg\nwarning: ignoring unsupported tag 'MERMAID_RENDER_MODE' at line 3328, file /home/jwakely/src/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/doc/doxygen/html.cfg\nwarning: ignoring unsupported tag 'MERMAID_JS_URL' at line 3346, file /home/jwakely/src/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/doc/doxygen/html.cfg\nwarning: ignoring unsupported tag 'MERMAIDFILE_DIRS' at line 3352, file /home/jwakely/src/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/doc/doxygen/html.cfg\n\n\nWe could just leave those new ones out of the file for now, so people\ncan use older versions. We don't care about any of those except maybe\nMARKDOWN_STRICT.\n\n\n libstdc++-v3/doc/doxygen/user.cfg.in | 1252 +++++++++++++++++++-------\n 1 file changed, 907 insertions(+), 345 deletions(-)","diff":"diff --git a/libstdc++-v3/doc/doxygen/user.cfg.in b/libstdc++-v3/doc/doxygen/user.cfg.in\nindex 8969bb8b9489..bdcb19c56faa 100644\n--- a/libstdc++-v3/doc/doxygen/user.cfg.in\n+++ b/libstdc++-v3/doc/doxygen/user.cfg.in\n@@ -1,7 +1,7 @@\n-# Doxyfile 1.8.20\n+# Doxyfile 1.17.0\n \n # This file describes the settings to be used by the documentation system\n-# doxygen (www.doxygen.org) for a project.\n+# Doxygen (www.doxygen.org) for a project.\n #\n # All text after a double hash (##) is considered a comment and is placed in\n # front of the TAG it is preceding.\n@@ -12,6 +12,16 @@\n # For lists, items can also be appended using:\n # TAG += value [value, ...]\n # Values that contain spaces should be placed between quotes (\\\" \\\").\n+#\n+# Note:\n+#\n+# Use Doxygen to compare the used configuration file with the template\n+# configuration file:\n+# doxygen -x [configFile]\n+# Use Doxygen to compare the used configuration file with the template\n+# configuration file without replacing the environment variables or CMake type\n+# replacement variables:\n+# doxygen -x_noenv [configFile]\n \n #---------------------------------------------------------------------------\n # Project related configuration options\n@@ -41,7 +51,7 @@ PROJECT_NAME = libstdc++\n PROJECT_NUMBER =\n \n # Using the PROJECT_BRIEF tag one can provide an optional one line description\n-# for a project that appears at the top of each page and should give viewer a\n+# for a project that appears at the top of each page and should give viewers a\n # quick idea about the purpose of the project. Keep the description short.\n \n PROJECT_BRIEF =\n@@ -53,24 +63,42 @@ PROJECT_BRIEF =\n \n PROJECT_LOGO =\n \n+# With the PROJECT_ICON tag one can specify an icon that is included in the tabs\n+# when the HTML document is shown. Doxygen will copy the logo to the output\n+# directory.\n+\n+PROJECT_ICON =\n+\n # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path\n # into which the generated documentation will be written. If a relative path is\n-# entered, it will be relative to the location where doxygen was started. If\n+# entered, it will be relative to the location where Doxygen was started. If\n # left blank the current directory will be used.\n \n OUTPUT_DIRECTORY = @outdir@\n \n-# If the CREATE_SUBDIRS tag is set to YES then doxygen will create 4096 sub-\n-# directories (in 2 levels) under the output directory of each output format and\n-# will distribute the generated files over these directories. Enabling this\n-# option can be useful when feeding doxygen a huge amount of source files, where\n-# putting all generated files in the same directory would otherwise causes\n-# performance problems for the file system.\n+# If the CREATE_SUBDIRS tag is set to YES then Doxygen will create up to 4096\n+# sub-directories (in 2 levels) under the output directory of each output format\n+# and will distribute the generated files over these directories. Enabling this\n+# option can be useful when feeding Doxygen a huge amount of source files, where\n+# putting all generated files in the same directory would otherwise cause\n+# performance problems for the file system. Adapt CREATE_SUBDIRS_LEVEL to\n+# control the number of sub-directories.\n # The default value is: NO.\n \n CREATE_SUBDIRS = NO\n \n-# If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII\n+# Controls the number of sub-directories that will be created when\n+# CREATE_SUBDIRS tag is set to YES. Level 0 represents 16 directories, and every\n+# level increment doubles the number of directories, resulting in 4096\n+# directories at level 8 which is the default and also the maximum value. The\n+# sub-directories are organized in 2 levels, the first level always has a fixed\n+# number of 16 directories.\n+# Minimum value: 0, maximum value: 8, default value: 8.\n+# This tag requires that the tag CREATE_SUBDIRS is set to YES.\n+\n+CREATE_SUBDIRS_LEVEL = 8\n+\n+# If the ALLOW_UNICODE_NAMES tag is set to YES, Doxygen will allow non-ASCII\n # characters to appear in the names of generated files. If set to NO, non-ASCII\n # characters will be escaped, for example _xE3_x81_x84 will be used for Unicode\n # U+3044.\n@@ -79,28 +107,28 @@ CREATE_SUBDIRS = NO\n ALLOW_UNICODE_NAMES = NO\n \n # The OUTPUT_LANGUAGE tag is used to specify the language in which all\n-# documentation generated by doxygen is written. Doxygen will use this\n+# documentation generated by Doxygen is written. Doxygen will use this\n # information to generate all constant output in the proper language.\n-# Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Catalan, Chinese,\n-# Chinese-Traditional, Croatian, Czech, Danish, Dutch, English (United States),\n-# Esperanto, Farsi (Persian), Finnish, French, German, Greek, Hungarian,\n-# Indonesian, Italian, Japanese, Japanese-en (Japanese with English messages),\n-# Korean, Korean-en (Korean with English messages), Latvian, Lithuanian,\n-# Macedonian, Norwegian, Persian (Farsi), Polish, Portuguese, Romanian, Russian,\n-# Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish, Swedish, Turkish,\n-# Ukrainian and Vietnamese.\n+# Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Bulgarian,\n+# Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch, English\n+# (United States), Esperanto, Farsi (Persian), Finnish, French, German, Greek,\n+# Hindi, Hungarian, Indonesian, Italian, Japanese, Japanese-en (Japanese with\n+# English messages), Korean, Korean-en (Korean with English messages), Latvian,\n+# Lithuanian, Macedonian, Norwegian, Persian (Farsi), Polish, Portuguese,\n+# Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish,\n+# Swedish, Turkish, Ukrainian and Vietnamese.\n # The default value is: English.\n \n OUTPUT_LANGUAGE = English\n \n-# If the BRIEF_MEMBER_DESC tag is set to YES, doxygen will include brief member\n+# If the BRIEF_MEMBER_DESC tag is set to YES, Doxygen will include brief member\n # descriptions after the members that are listed in the file and class\n # documentation (similar to Javadoc). Set to NO to disable this.\n # The default value is: YES.\n \n BRIEF_MEMBER_DESC = @do_man@\n \n-# If the REPEAT_BRIEF tag is set to YES, doxygen will prepend the brief\n+# If the REPEAT_BRIEF tag is set to YES, Doxygen will prepend the brief\n # description of a member or function before the detailed description\n #\n # Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the\n@@ -121,13 +149,13 @@ REPEAT_BRIEF = YES\n ABBREVIATE_BRIEF =\n \n # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then\n-# doxygen will generate a detailed section even if there is only a brief\n+# Doxygen will generate a detailed section even if there is only a brief\n # description.\n # The default value is: NO.\n \n ALWAYS_DETAILED_SEC = YES\n \n-# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all\n+# If the INLINE_INHERITED_MEMB tag is set to YES, Doxygen will show all\n # inherited members of a class in the documentation of that class as if those\n # members were ordinary class members. Constructors, destructors and assignment\n # operators of the base classes will not be shown.\n@@ -135,7 +163,7 @@ ALWAYS_DETAILED_SEC = YES\n \n INLINE_INHERITED_MEMB = YES\n \n-# If the FULL_PATH_NAMES tag is set to YES, doxygen will prepend the full path\n+# If the FULL_PATH_NAMES tag is set to YES, Doxygen will prepend the full path\n # before files name in the file list and in the header files. If set to NO the\n # shortest path that makes the file name unique will be used\n # The default value is: YES.\n@@ -145,11 +173,11 @@ FULL_PATH_NAMES = NO\n # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.\n # Stripping is only done if one of the specified strings matches the left-hand\n # part of the path. The tag can be used to show relative paths in the file list.\n-# If left blank the directory from which doxygen is run is used as the path to\n+# If left blank the directory from which Doxygen is run is used as the path to\n # strip.\n #\n # Note that you can specify absolute paths here, but also relative paths, which\n-# will be relative from the directory where doxygen is started.\n+# will be relative from the directory where Doxygen is started.\n # This tag requires that the tag FULL_PATH_NAMES is set to YES.\n \n STRIP_FROM_PATH = @srcdir@/doc/ @srcdir@/libsupc++/ include/\n@@ -163,41 +191,42 @@ STRIP_FROM_PATH = @srcdir@/doc/ @srcdir@/libsupc++/ include/\n \n STRIP_FROM_INC_PATH =\n \n-# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but\n-# less readable) file names. This can be useful is your file systems doesn't\n+# If the SHORT_NAMES tag is set to YES, Doxygen will generate much shorter (but\n+# less readable) file names. This can be useful if your file system doesn't\n # support long names like on DOS, Mac, or CD-ROM.\n # The default value is: NO.\n \n SHORT_NAMES = @shortname@\n \n-# If the JAVADOC_AUTOBRIEF tag is set to YES then doxygen will interpret the\n-# first line (until the first dot) of a Javadoc-style comment as the brief\n-# description. If set to NO, the Javadoc-style will behave just like regular Qt-\n-# style comments (thus requiring an explicit @brief command for a brief\n-# description.)\n+# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen will interpret the\n+# first line (until the first dot, question mark or exclamation mark) of a\n+# Javadoc-style comment as the brief description. If set to NO, the Javadoc-\n+# style will behave just like regular Qt-style comments (thus requiring an\n+# explicit @brief command for a brief description.)\n # The default value is: NO.\n \n JAVADOC_AUTOBRIEF = NO\n \n-# If the JAVADOC_BANNER tag is set to YES then doxygen will interpret a line\n+# If the JAVADOC_BANNER tag is set to YES then Doxygen will interpret a line\n # such as\n # /***************\n # as being the beginning of a Javadoc-style comment \"banner\". If set to NO, the\n # Javadoc-style will behave just like regular comments and it will not be\n-# interpreted by doxygen.\n+# interpreted by Doxygen.\n # The default value is: NO.\n \n JAVADOC_BANNER = NO\n \n-# If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first\n-# line (until the first dot) of a Qt-style comment as the brief description. If\n-# set to NO, the Qt-style will behave just like regular Qt-style comments (thus\n-# requiring an explicit \\brief command for a brief description.)\n+# If the QT_AUTOBRIEF tag is set to YES then Doxygen will interpret the first\n+# line (until the first dot, question mark or exclamation mark) of a Qt-style\n+# comment as the brief description. If set to NO, the Qt-style will behave just\n+# like regular Qt-style comments (thus requiring an explicit \\brief command for\n+# a brief description.)\n # The default value is: NO.\n \n QT_AUTOBRIEF = NO\n \n-# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make doxygen treat a\n+# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen treat a\n # multi-line C++ special comment block (i.e. a block of //! or /// comments) as\n # a brief description. This used to be the default behavior. The new default is\n # to treat a multi-line C++ comment block as a detailed description. Set this\n@@ -209,10 +238,10 @@ QT_AUTOBRIEF = NO\n \n MULTILINE_CPP_IS_BRIEF = YES\n \n-# By default Python docstrings are displayed as preformatted text and doxygen's\n+# By default Python docstrings are displayed as preformatted text and Doxygen's\n # special commands cannot be used. By setting PYTHON_DOCSTRING to NO the\n-# doxygen's special commands can be used and the contents of the docstring\n-# documentation blocks is shown as doxygen documentation.\n+# Doxygen's special commands can be used and the contents of the docstring\n+# documentation blocks is shown as Doxygen documentation.\n # The default value is: YES.\n \n PYTHON_DOCSTRING = YES\n@@ -223,7 +252,7 @@ PYTHON_DOCSTRING = YES\n \n INHERIT_DOCS = YES\n \n-# If the SEPARATE_MEMBER_PAGES tag is set to YES then doxygen will produce a new\n+# If the SEPARATE_MEMBER_PAGES tag is set to YES then Doxygen will produce a new\n # page for each member. If set to NO, the documentation of a member will be part\n # of the file/class/namespace that contains it.\n # The default value is: NO.\n@@ -240,16 +269,16 @@ TAB_SIZE = 8\n # the documentation. An alias has the form:\n # name=value\n # For example adding\n-# \"sideeffect=@par Side Effects:\\n\"\n+# \"sideeffect=@par Side Effects:^^\"\n # will allow you to put the command \\sideeffect (or @sideeffect) in the\n # documentation, which will result in a user-defined paragraph with heading\n-# \"Side Effects:\". You can put \\n's in the value part of an alias to insert\n-# newlines (in the resulting output). You can put ^^ in the value part of an\n-# alias to insert a newline as if a physical newline was in the original file.\n-# When you need a literal { or } or , in the value part of an alias you have to\n-# escape them by means of a backslash (\\), this can lead to conflicts with the\n-# commands \\{ and \\} for these it is advised to use the version @{ and @} or use\n-# a double escape (\\\\{ and \\\\})\n+# \"Side Effects:\". Note that you cannot put \\n's in the value part of an alias\n+# to insert newlines (in the resulting output). You can put ^^ in the value part\n+# of an alias to insert a newline as if a physical newline was in the original\n+# file. When you need a literal { or } or , in the value part of an alias you\n+# have to escape them by means of a backslash (\\), this can lead to conflicts\n+# with the commands \\{ and \\} for these it is advised to use the version @{ and\n+# @} or use a double escape (\\\\{ and \\\\})\n \n ALIASES = \"doctodo=@todo Needs documentation! See http://gcc.gnu.org/onlinedocs/libstdc++/manual/documentation_style.html\" \\\n \"headername{1}=Instead, include \\<\\1\\>.\" \\\n@@ -295,58 +324,95 @@ OPTIMIZE_OUTPUT_SLICE = NO\n # parses. With this tag you can assign which parser to use for a given\n # extension. Doxygen has a built-in mapping, but you can override or extend it\n # using this tag. The format is ext=language, where ext is a file extension, and\n-# language is one of the parsers supported by doxygen: IDL, Java, JavaScript,\n-# Csharp (C#), C, C++, D, PHP, md (Markdown), Objective-C, Python, Slice, VHDL,\n-# Fortran (fixed format Fortran: FortranFixed, free formatted Fortran:\n+# language is one of the parsers supported by Doxygen: IDL, Java, JavaScript,\n+# Csharp (C#), C, C++, Lex, D, PHP, md (Markdown), Objective-C, Python, Slice,\n+# VHDL, Fortran (fixed format Fortran: FortranFixed, free formatted Fortran:\n # FortranFree, unknown formatted Fortran: Fortran. In the later case the parser\n # tries to guess whether the code is fixed or free formatted code, this is the\n-# default for Fortran type files). For instance to make doxygen treat .inc files\n+# default for Fortran type files). For instance to make Doxygen treat .inc files\n # as Fortran files (default is PHP), and .f files as C (default is Fortran),\n # use: inc=Fortran f=C.\n #\n # Note: For files without extension you can use no_extension as a placeholder.\n #\n # Note that for custom extensions you also need to set FILE_PATTERNS otherwise\n-# the files are not read by doxygen.\n+# the files are not read by Doxygen. When specifying no_extension you should add\n+# * to the FILE_PATTERNS.\n+#\n+# Note see also the list of default file extension mappings.\n \n EXTENSION_MAPPING = no_extension=C++ \\\n .h=C++ \\\n .tcc=C++ \\\n .hpp=C++\n \n-# If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments\n+# If the MARKDOWN_SUPPORT tag is enabled then Doxygen pre-processes all comments\n # according to the Markdown format, which allows for more readable\n # documentation. See https://daringfireball.net/projects/markdown/ for details.\n-# The output of markdown processing is further processed by doxygen, so you can\n-# mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in\n+# The output of markdown processing is further processed by Doxygen, so you can\n+# mix Doxygen, HTML, and XML commands with Markdown formatting. Disable only in\n # case of backward compatibilities issues.\n # The default value is: YES.\n \n MARKDOWN_SUPPORT = YES\n \n+# If the MARKDOWN_STRICT tag is enabled then Doxygen treats text in comments as\n+# Markdown formatted also in cases where Doxygen's native markup format\n+# conflicts with that of Markdown. This is only relevant in cases where\n+# backticks are used. Doxygen's native markup style allows a single quote to end\n+# a text fragment started with a backtick and then treat it as a piece of quoted\n+# text, whereas in Markdown such text fragment is treated as verbatim and only\n+# ends when a second matching backtick is found. Also, Doxygen's native markup\n+# format requires double quotes to be escaped when they appear in a backtick\n+# section, whereas this is not needed for Markdown.\n+# The default value is: YES.\n+# This tag requires that the tag MARKDOWN_SUPPORT is set to YES.\n+\n+MARKDOWN_STRICT = YES\n+\n # When the TOC_INCLUDE_HEADINGS tag is set to a non-zero value, all headings up\n # to that level are automatically included in the table of contents, even if\n # they do not have an id attribute.\n # Note: This feature currently applies only to Markdown headings.\n-# Minimum value: 0, maximum value: 99, default value: 5.\n+# Minimum value: 0, maximum value: 99, default value: 6.\n # This tag requires that the tag MARKDOWN_SUPPORT is set to YES.\n \n TOC_INCLUDE_HEADINGS = 0\n \n-# When enabled doxygen tries to link words that correspond to documented\n+# The MARKDOWN_ID_STYLE tag can be used to specify the algorithm used to\n+# generate identifiers for the Markdown headings. Note: Every identifier is\n+# unique.\n+# Possible values are: DOXYGEN use a fixed 'autotoc_md' string followed by a\n+# sequence number starting at 0 and GITHUB use the lower case version of title\n+# with any whitespace replaced by '-' and punctuation characters removed.\n+# The default value is: DOXYGEN.\n+# This tag requires that the tag MARKDOWN_SUPPORT is set to YES.\n+\n+MARKDOWN_ID_STYLE = DOXYGEN\n+\n+# When enabled Doxygen tries to link words that correspond to documented\n # classes, or namespaces to their corresponding documentation. Such a link can\n # be prevented in individual cases by putting a % sign in front of the word or\n-# globally by setting AUTOLINK_SUPPORT to NO.\n+# globally by setting AUTOLINK_SUPPORT to NO. Words listed in the\n+# AUTOLINK_IGNORE_WORDS tag are excluded from automatic linking.\n # The default value is: YES.\n \n AUTOLINK_SUPPORT = NO\n \n+# This tag specifies a list of words that, when matching the start of a word in\n+# the documentation, will suppress auto links generation, if it is enabled via\n+# AUTOLINK_SUPPORT. This list does not affect links explicitly created using #\n+# or the \\link or \\ref commands.\n+# This tag requires that the tag AUTOLINK_SUPPORT is set to YES.\n+\n+AUTOLINK_IGNORE_WORDS =\n+\n # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want\n # to include (a tag file for) the STL sources as input, then you should set this\n-# tag to YES in order to let doxygen match functions declarations and\n+# tag to YES in order to let Doxygen match functions declarations and\n # definitions whose arguments contain STL classes (e.g. func(std::string);\n-# versus func(std::string) {}). This also make the inheritance and collaboration\n-# diagrams that involve STL classes more complete and accurate.\n+# versus func(std::string) {}). This also makes the inheritance and\n+# collaboration diagrams that involve STL classes more complete and accurate.\n # The default value is: NO.\n \n BUILTIN_STL_SUPPORT = NO\n@@ -358,16 +424,16 @@ BUILTIN_STL_SUPPORT = NO\n CPP_CLI_SUPPORT = NO\n \n # Set the SIP_SUPPORT tag to YES if your project consists of sip (see:\n-# https://www.riverbankcomputing.com/software/sip/intro) sources only. Doxygen\n-# will parse them like normal C++ but will assume all classes use public instead\n-# of private inheritance when no explicit protection keyword is present.\n+# https://www.riverbankcomputing.com/software) sources only. Doxygen will parse\n+# them like normal C++ but will assume all classes use public instead of private\n+# inheritance when no explicit protection keyword is present.\n # The default value is: NO.\n \n SIP_SUPPORT = NO\n \n # For Microsoft's IDL there are propget and propput attributes to indicate\n # getter and setter methods for a property. Setting this option to YES will make\n-# doxygen to replace the get and set methods by a property in the documentation.\n+# Doxygen to replace the get and set methods by a property in the documentation.\n # This will only work if the methods are indeed getting or setting a simple\n # type. If this is not the case, or you want to show the methods anyway, you\n # should set this option to NO.\n@@ -376,7 +442,7 @@ SIP_SUPPORT = NO\n IDL_PROPERTY_SUPPORT = NO\n \n # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC\n-# tag is set to YES then doxygen will reuse the documentation of the first\n+# tag is set to YES then Doxygen will reuse the documentation of the first\n # member in the group (if any) for the other members of the group. By default\n # all members of a group must be documented explicitly.\n # The default value is: NO.\n@@ -434,34 +500,42 @@ TYPEDEF_HIDES_STRUCT = NO\n # The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This\n # cache is used to resolve symbols given their name and scope. Since this can be\n # an expensive process and often the same symbol appears multiple times in the\n-# code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small\n-# doxygen will become slower. If the cache is too large, memory is wasted. The\n+# code, Doxygen keeps a cache of pre-resolved symbols. If the cache is too small\n+# Doxygen will become slower. If the cache is too large, memory is wasted. The\n # cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range\n # is 0..9, the default is 0, corresponding to a cache size of 2^16=65536\n-# symbols. At the end of a run doxygen will report the cache usage and suggest\n+# symbols. At the end of a run Doxygen will report the cache usage and suggest\n # the optimal cache size from a speed point of view.\n # Minimum value: 0, maximum value: 9, default value: 0.\n \n LOOKUP_CACHE_SIZE = 0\n \n-# The NUM_PROC_THREADS specifies the number threads doxygen is allowed to use\n-# during processing. When set to 0 doxygen will based this on the number of\n+# The NUM_PROC_THREADS specifies the number of threads Doxygen is allowed to use\n+# during processing. When set to 0 Doxygen will based this on the number of\n # cores available in the system. You can set it explicitly to a value larger\n # than 0 to get more control over the balance between CPU load and processing\n # speed. At this moment only the input processing can be done using multiple\n # threads. Since this is still an experimental feature the default is set to 1,\n-# which efficively disables parallel processing. Please report any issues you\n+# which effectively disables parallel processing. Please report any issues you\n # encounter. Generating dot graphs in parallel is controlled by the\n # DOT_NUM_THREADS setting.\n-# Minimum value: 0, maximum value: 32, default value: 1.\n+# Minimum value: 0, maximum value: 512, default value: 1.\n \n NUM_PROC_THREADS = 1\n \n+# If the TIMESTAMP tag is set different from NO then each generated page will\n+# contain the date or date and time when the page was generated. Setting this to\n+# NO can help when comparing the output of multiple runs.\n+# Possible values are: YES, NO, DATETIME and DATE.\n+# The default value is: NO.\n+\n+TIMESTAMP = NO\n+\n #---------------------------------------------------------------------------\n # Build related configuration options\n #---------------------------------------------------------------------------\n \n-# If the EXTRACT_ALL tag is set to YES, doxygen will assume all entities in\n+# If the EXTRACT_ALL tag is set to YES, Doxygen will assume all entities in\n # documentation are documented, even if no documentation was available. Private\n # class members and static file members will be hidden unless the\n # EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES.\n@@ -520,7 +594,14 @@ EXTRACT_LOCAL_METHODS = YES\n \n EXTRACT_ANON_NSPACES = NO\n \n-# If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all\n+# If this flag is set to YES, the name of an unnamed parameter in a declaration\n+# will be determined by the corresponding definition. By default unnamed\n+# parameters remain unnamed in the output.\n+# The default value is: YES.\n+\n+RESOLVE_UNNAMED_PARAMS = YES\n+\n+# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all\n # undocumented members inside documented classes or files. If set to NO these\n # members will be included in the various overviews, but no documentation\n # section is generated. This option has no effect if EXTRACT_ALL is enabled.\n@@ -528,22 +609,31 @@ EXTRACT_ANON_NSPACES = NO\n \n HIDE_UNDOC_MEMBERS = NO\n \n-# If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all\n+# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all\n # undocumented classes that are normally visible in the class hierarchy. If set\n # to NO, these classes will be included in the various overviews. This option\n-# has no effect if EXTRACT_ALL is enabled.\n+# will also hide undocumented C++ concepts if enabled. This option has no effect\n+# if EXTRACT_ALL is enabled.\n # The default value is: NO.\n \n HIDE_UNDOC_CLASSES = YES\n \n-# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend\n+# If the HIDE_UNDOC_NAMESPACES tag is set to YES, Doxygen will hide all\n+# undocumented namespaces that are normally visible in the namespace hierarchy.\n+# If set to NO, these namespaces will be included in the various overviews. This\n+# option has no effect if EXTRACT_ALL is enabled.\n+# The default value is: YES.\n+\n+HIDE_UNDOC_NAMESPACES = YES\n+\n+# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all friend\n # declarations. If set to NO, these declarations will be included in the\n # documentation.\n # The default value is: NO.\n \n HIDE_FRIEND_COMPOUNDS = NO\n \n-# If the HIDE_IN_BODY_DOCS tag is set to YES, doxygen will hide any\n+# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any\n # documentation blocks found inside the body of a function. If set to NO, these\n # blocks will be appended to the function's detailed documentation block.\n # The default value is: NO.\n@@ -557,23 +647,31 @@ HIDE_IN_BODY_DOCS = NO\n \n INTERNAL_DOCS = NO\n \n-# If the CASE_SENSE_NAMES tag is set to NO then doxygen will only generate file\n-# names in lower-case letters. If set to YES, upper-case letters are also\n-# allowed. This is useful if you have classes or files whose names only differ\n-# in case and if your file system supports case sensitive file names. Windows\n-# (including Cygwin) and Mac users are advised to set this option to NO.\n-# The default value is: system dependent.\n+# With the correct setting of option CASE_SENSE_NAMES Doxygen will better be\n+# able to match the capabilities of the underlying filesystem. In case the\n+# filesystem is case sensitive (i.e. it supports files in the same directory\n+# whose names only differ in casing), the option must be set to YES to properly\n+# deal with such files in case they appear in the input. For filesystems that\n+# are not case sensitive the option should be set to NO to properly deal with\n+# output files written for symbols that only differ in casing, such as for two\n+# classes, one named CLASS and the other named Class, and to also support\n+# references to files without having to specify the exact matching casing. On\n+# Windows (including Cygwin) and macOS, users should typically set this option\n+# to NO, whereas on Linux or other Unix flavors it should typically be set to\n+# YES.\n+# Possible values are: SYSTEM, NO and YES.\n+# The default value is: SYSTEM.\n \n CASE_SENSE_NAMES = NO\n \n-# If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with\n+# If the HIDE_SCOPE_NAMES tag is set to NO then Doxygen will show members with\n # their full class and namespace scopes in the documentation. If set to YES, the\n # scope will be hidden.\n # The default value is: NO.\n \n HIDE_SCOPE_NAMES = NO\n \n-# If the HIDE_COMPOUND_REFERENCE tag is set to NO (default) then doxygen will\n+# If the HIDE_COMPOUND_REFERENCE tag is set to NO (default) then Doxygen will\n # append additional text to a page's title, such as Class Reference. If set to\n # YES the compound reference will be hidden.\n # The default value is: NO.\n@@ -586,7 +684,7 @@ HIDE_COMPOUND_REFERENCE= NO\n \n SHOW_HEADERFILE = YES\n \n-# If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of\n+# If the SHOW_INCLUDE_FILES tag is set to YES then Doxygen will put a list of\n # the files that are included by a file in the documentation of that file.\n # The default value is: YES.\n \n@@ -599,7 +697,7 @@ SHOW_INCLUDE_FILES = NO\n \n SHOW_GROUPED_MEMB_INC = NO\n \n-# If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include\n+# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen will list include\n # files with double quotes in the documentation rather than with sharp brackets.\n # The default value is: NO.\n \n@@ -611,14 +709,14 @@ FORCE_LOCAL_INCLUDES = NO\n \n INLINE_INFO = YES\n \n-# If the SORT_MEMBER_DOCS tag is set to YES then doxygen will sort the\n+# If the SORT_MEMBER_DOCS tag is set to YES then Doxygen will sort the\n # (detailed) documentation of file and class members alphabetically by member\n # name. If set to NO, the members will appear in declaration order.\n # The default value is: YES.\n \n SORT_MEMBER_DOCS = YES\n \n-# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief\n+# If the SORT_BRIEF_DOCS tag is set to YES then Doxygen will sort the brief\n # descriptions of file, namespace and class members alphabetically by member\n # name. If set to NO, the members will appear in declaration order. Note that\n # this will also influence the order of the classes in the class list.\n@@ -626,7 +724,7 @@ SORT_MEMBER_DOCS = YES\n \n SORT_BRIEF_DOCS = YES\n \n-# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the\n+# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then Doxygen will sort the\n # (brief and detailed) documentation of class members so that constructors and\n # destructors are listed first. If set to NO the constructors will appear in the\n # respective orders defined by SORT_BRIEF_DOCS and SORT_MEMBER_DOCS.\n@@ -638,7 +736,7 @@ SORT_BRIEF_DOCS = YES\n \n SORT_MEMBERS_CTORS_1ST = YES\n \n-# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the hierarchy\n+# If the SORT_GROUP_NAMES tag is set to YES then Doxygen will sort the hierarchy\n # of group names into alphabetical order. If set to NO the group names will\n # appear in their defined order.\n # The default value is: NO.\n@@ -655,11 +753,11 @@ SORT_GROUP_NAMES = YES\n \n SORT_BY_SCOPE_NAME = NO\n \n-# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper\n+# If the STRICT_PROTO_MATCHING option is enabled and Doxygen fails to do proper\n # type resolution of all parameters of a function it will reject a match between\n # the prototype and the implementation of a member function even if there is\n # only one candidate or it is obvious which candidate to choose by doing a\n-# simple string match. By disabling STRICT_PROTO_MATCHING doxygen will still\n+# simple string match. By disabling STRICT_PROTO_MATCHING Doxygen will still\n # accept a match between prototype and implementation in such cases.\n # The default value is: NO.\n \n@@ -690,6 +788,27 @@ GENERATE_BUGLIST = NO\n \n GENERATE_DEPRECATEDLIST= YES\n \n+# The GENERATE_REQUIREMENTS tag can be used to enable (YES) or disable (NO) the\n+# requirements page. When enabled, this page is automatically created when at\n+# least one comment block with a \\requirement command appears in the input.\n+# The default value is: YES.\n+\n+GENERATE_REQUIREMENTS = YES\n+\n+# The REQ_TRACEABILITY_INFO tag controls if traceability information is shown on\n+# the requirements page (only relevant when using \\requirement comment blocks).\n+# The setting NO will disable the traceability information altogether. The\n+# setting UNSATISFIED_ONLY will show a list of requirements that are missing a\n+# satisfies relation (through the command: \\satisfies). Similarly the setting\n+# UNVERIFIED_ONLY will show a list of requirements that are missing a verifies\n+# relation (through the command: \\verifies). Setting the tag to YES (the\n+# default) will show both lists if applicable.\n+# Possible values are: YES, NO, UNSATISFIED_ONLY and UNVERIFIED_ONLY.\n+# The default value is: YES.\n+# This tag requires that the tag GENERATE_REQUIREMENTS is set to YES.\n+\n+REQ_TRACEABILITY_INFO = YES\n+\n # The ENABLED_SECTIONS tag can be used to enable conditional documentation\n # sections, marked by \\if ... \\endif and \\cond \n # ... \\endcond blocks.\n@@ -729,24 +848,25 @@ SHOW_FILES = YES\n SHOW_NAMESPACES = YES\n \n # The FILE_VERSION_FILTER tag can be used to specify a program or script that\n-# doxygen should invoke to get the current version for each file (typically from\n+# Doxygen should invoke to get the current version for each file (typically from\n # the version control system). Doxygen will invoke the program by executing (via\n # popen()) the command command input-file, where command is the value of the\n # FILE_VERSION_FILTER tag, and input-file is the name of an input file provided\n-# by doxygen. Whatever the program writes to standard output is used as the file\n+# by Doxygen. Whatever the program writes to standard output is used as the file\n # version. For an example see the documentation.\n \n FILE_VERSION_FILTER =\n \n # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed\n-# by doxygen. The layout file controls the global structure of the generated\n+# by Doxygen. The layout file controls the global structure of the generated\n # output files in an output format independent way. To create the layout file\n-# that represents doxygen's defaults, run doxygen with the -l option. You can\n+# that represents Doxygen's defaults, run Doxygen with the -l option. You can\n # optionally specify a file name after the option, if omitted DoxygenLayout.xml\n-# will be used as the name of the layout file.\n+# will be used as the name of the layout file. See also section \"Changing the\n+# layout of pages\" for information.\n #\n-# Note that if you run doxygen from a directory containing a file called\n-# DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE\n+# Note that if you run Doxygen from a directory containing a file called\n+# DoxygenLayout.xml, Doxygen will parse it automatically even if the LAYOUT_FILE\n # tag is left empty.\n \n LAYOUT_FILE =\n@@ -761,19 +881,35 @@ LAYOUT_FILE =\n \n CITE_BIB_FILES =\n \n+# The EXTERNAL_TOOL_PATH tag can be used to extend the search path (PATH\n+# environment variable) so that external tools such as latex and gs can be\n+# found.\n+# Note: Directories specified with EXTERNAL_TOOL_PATH are added in front of the\n+# path already specified by the PATH variable, and are added in the order\n+# specified.\n+# Note: This option is particularly useful for macOS version 14 (Sonoma) and\n+# higher, when running Doxygen from Doxywizard, because in this case any user-\n+# defined changes to the PATH are ignored. A typical example on macOS is to set\n+# EXTERNAL_TOOL_PATH = /Library/TeX/texbin /usr/local/bin\n+# together with the standard path, the full search path used by doxygen when\n+# launching external tools will then become\n+# PATH=/Library/TeX/texbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin\n+\n+EXTERNAL_TOOL_PATH =\n+\n #---------------------------------------------------------------------------\n # Configuration options related to warning and progress messages\n #---------------------------------------------------------------------------\n \n # The QUIET tag can be used to turn on/off the messages that are generated to\n-# standard output by doxygen. If QUIET is set to YES this implies that the\n+# standard output by Doxygen. If QUIET is set to YES this implies that the\n # messages are off.\n # The default value is: NO.\n \n QUIET = YES\n \n # The WARNINGS tag can be used to turn on/off the warning messages that are\n-# generated to standard error (stderr) by doxygen. If WARNINGS is set to YES\n+# generated to standard error (stderr) by Doxygen. If WARNINGS is set to YES\n # this implies that the warnings are on.\n #\n # Tip: Turn warnings on while writing the documentation.\n@@ -781,49 +917,97 @@ QUIET = YES\n \n WARNINGS = YES\n \n-# If the WARN_IF_UNDOCUMENTED tag is set to YES then doxygen will generate\n+# If the WARN_IF_UNDOCUMENTED tag is set to YES then Doxygen will generate\n # warnings for undocumented members. If EXTRACT_ALL is set to YES then this flag\n # will automatically be disabled.\n # The default value is: YES.\n \n WARN_IF_UNDOCUMENTED = NO\n \n-# If the WARN_IF_DOC_ERROR tag is set to YES, doxygen will generate warnings for\n-# potential errors in the documentation, such as not documenting some parameters\n-# in a documented function, or documenting parameters that don't exist or using\n-# markup commands wrongly.\n+# If the WARN_IF_DOC_ERROR tag is set to YES, Doxygen will generate warnings for\n+# potential errors in the documentation, such as documenting some parameters in\n+# a documented function twice, or documenting parameters that don't exist or\n+# using markup commands wrongly.\n # The default value is: YES.\n \n WARN_IF_DOC_ERROR = YES\n \n+# If WARN_IF_INCOMPLETE_DOC is set to YES, Doxygen will warn about incomplete\n+# function parameter documentation. If set to NO, Doxygen will accept that some\n+# parameters have no documentation without warning.\n+# The default value is: YES.\n+\n+WARN_IF_INCOMPLETE_DOC = YES\n+\n # This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that\n # are documented, but have no documentation for their parameters or return\n-# value. If set to NO, doxygen will only warn about wrong or incomplete\n-# parameter documentation, but not about the absence of documentation. If\n-# EXTRACT_ALL is set to YES then this flag will automatically be disabled.\n+# value. If set to NO, Doxygen will only warn about wrong parameter\n+# documentation, but not about the absence of documentation. If EXTRACT_ALL is\n+# set to YES then this flag will automatically be disabled. See also\n+# WARN_IF_INCOMPLETE_DOC\n # The default value is: NO.\n \n WARN_NO_PARAMDOC = NO\n \n-# If the WARN_AS_ERROR tag is set to YES then doxygen will immediately stop when\n-# a warning is encountered.\n+# If WARN_IF_UNDOC_ENUM_VAL option is set to YES, Doxygen will warn about\n+# undocumented enumeration values. If set to NO, Doxygen will accept\n+# undocumented enumeration values. If EXTRACT_ALL is set to YES then this flag\n+# will automatically be disabled.\n+# The default value is: NO.\n+\n+WARN_IF_UNDOC_ENUM_VAL = NO\n+\n+# If WARN_LAYOUT_FILE option is set to YES, Doxygen will warn about issues found\n+# while parsing the user defined layout file, such as missing or wrong elements.\n+# See also LAYOUT_FILE for details. If set to NO, problems with the layout file\n+# will be suppressed.\n+# The default value is: YES.\n+\n+WARN_LAYOUT_FILE = YES\n+\n+# If the WARN_AS_ERROR tag is set to YES then Doxygen will immediately stop when\n+# a warning is encountered. If the WARN_AS_ERROR tag is set to FAIL_ON_WARNINGS\n+# then Doxygen will continue running as if WARN_AS_ERROR tag is set to NO, but\n+# at the end of the Doxygen process Doxygen will return with a non-zero status.\n+# If the WARN_AS_ERROR tag is set to FAIL_ON_WARNINGS_PRINT then Doxygen behaves\n+# like FAIL_ON_WARNINGS but in case no WARN_LOGFILE is defined Doxygen will not\n+# write the warning messages in between other messages but write them at the end\n+# of a run, in case a WARN_LOGFILE is defined the warning messages will be\n+# besides being in the defined file also be shown at the end of a run, unless\n+# the WARN_LOGFILE is defined as - i.e. standard output (stdout) in that case\n+# the behavior will remain as with the setting FAIL_ON_WARNINGS.\n+# Possible values are: NO, YES, FAIL_ON_WARNINGS and FAIL_ON_WARNINGS_PRINT.\n # The default value is: NO.\n \n WARN_AS_ERROR = NO\n \n-# The WARN_FORMAT tag determines the format of the warning messages that doxygen\n+# The WARN_FORMAT tag determines the format of the warning messages that Doxygen\n # can produce. The string should contain the $file, $line, and $text tags, which\n # will be replaced by the file and line number from which the warning originated\n # and the warning text. Optionally the format may contain $version, which will\n # be replaced by the version of the file (if it could be obtained via\n # FILE_VERSION_FILTER)\n+# See also: WARN_LINE_FORMAT\n # The default value is: $file:$line: $text.\n \n-WARN_FORMAT = \"$file:$line: $text \"\n+WARN_FORMAT = \"$file:$line: $text \"\n+\n+# In the $text part of the WARN_FORMAT command it is possible that a reference\n+# to a more specific place is given. To make it easier to jump to this place\n+# (outside of Doxygen) the user can define a custom \"cut\" / \"paste\" string.\n+# Example:\n+# WARN_LINE_FORMAT = \"'vi $file +$line'\"\n+# See also: WARN_FORMAT\n+# The default value is: at line $line of file $file.\n+\n+WARN_LINE_FORMAT = \"at line $line of file $file\"\n \n # The WARN_LOGFILE tag can be used to specify a file to which warning and error\n # messages should be written. If left blank the output is written to standard\n-# error (stderr).\n+# error (stderr). In case the file specified cannot be opened for writing the\n+# warning and error messages are written to standard error. When as file - is\n+# specified the warning and error messages are written to standard output\n+# (stdout).\n \n WARN_LOGFILE =\n \n@@ -1061,29 +1245,42 @@ INPUT = @srcdir@/doc/doxygen/doxygroups.cc \\\n include/ext/pb_ds/detail/unordered_iterator\n \n # This tag can be used to specify the character encoding of the source files\n-# that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses\n+# that Doxygen parses. Internally Doxygen uses the UTF-8 encoding. Doxygen uses\n # libiconv (or the iconv built into libc) for the transcoding. See the libiconv\n-# documentation (see: https://www.gnu.org/software/libiconv/) for the list of\n-# possible encodings.\n+# documentation (see:\n+# https://www.gnu.org/software/libiconv/) for the list of possible encodings.\n+# See also: INPUT_FILE_ENCODING\n # The default value is: UTF-8.\n \n INPUT_ENCODING = UTF-8\n \n+# This tag can be used to specify the character encoding of the source files\n+# that Doxygen parses. The INPUT_FILE_ENCODING tag can be used to specify\n+# character encoding on a per file pattern basis. Doxygen will compare the file\n+# name with each pattern and apply the encoding instead of the default\n+# INPUT_ENCODING if there is a match. The character encodings are a list of the\n+# form: pattern=encoding (like *.php=ISO-8859-1).\n+# See also: INPUT_ENCODING for further information on supported encodings.\n+\n+INPUT_FILE_ENCODING =\n+\n # If the value of the INPUT tag contains directories, you can use the\n # FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and\n # *.h) to filter out the source-files in the directories.\n #\n # Note that for custom extensions or not directly supported extensions you also\n # need to set EXTENSION_MAPPING for the extension otherwise the files are not\n-# read by doxygen.\n+# read by Doxygen.\n #\n-# If left blank the following patterns are tested:*.c, *.cc, *.cxx, *.cpp,\n-# *.c++, *.java, *.ii, *.ixx, *.ipp, *.i++, *.inl, *.idl, *.ddl, *.odl, *.h,\n-# *.hh, *.hxx, *.hpp, *.h++, *.cs, *.d, *.php, *.php4, *.php5, *.phtml, *.inc,\n-# *.m, *.markdown, *.md, *.mm, *.dox (to be provided as doxygen C comment),\n-# *.doc (to be provided as doxygen C comment), *.txt (to be provided as doxygen\n-# C comment), *.py, *.pyw, *.f90, *.f95, *.f03, *.f08, *.f18, *.f, *.for, *.vhd,\n-# *.vhdl, *.ucf, *.qsf and *.ice.\n+# Note the list of default checked file patterns might differ from the list of\n+# default file extension mappings.\n+#\n+# If left blank the following patterns are tested:*.c, *.cc, *.cxx, *.cxxm,\n+# *.cpp, *.cppm, *.ccm, *.c++, *.c++m, *.java, *.ii, *.ixx, *.ipp, *.i++, *.inl,\n+# *.idl, *.ddl, *.odl, *.h, *.hh, *.hxx, *.hpp, *.h++, *.l, *.cs, *.d, *.php,\n+# *.php4, *.php5, *.phtml, *.inc, *.m, *.markdown, *.md, *.mm, *.dox (to be\n+# provided as Doxygen C comment), *.py, *.pyw, *.f90, *.f95, *.f03, *.f08,\n+# *.f18, *.f, *.for, *.vhd, *.vhdl, *.ucf, *.qsf and *.ice.\n \n FILE_PATTERNS = *.h \\\n *.hpp \\\n@@ -1099,7 +1296,7 @@ RECURSIVE = NO\n # excluded from the INPUT source files. This way you can easily exclude a\n # subdirectory from a directory tree whose root is specified with the INPUT tag.\n #\n-# Note that relative paths are relative to the directory from which doxygen is\n+# Note that relative paths are relative to the directory from which Doxygen is\n # run.\n \n EXCLUDE = Makefile \\\n@@ -1131,8 +1328,8 @@ EXCLUDE_PATTERNS = stamp-* \\\n # (namespaces, classes, functions, etc.) that should be excluded from the\n # output. The symbol name can be a fully qualified name, a word, or if the\n # wildcard * is used, a substring. Examples: ANamespace, AClass,\n-# AClass::ANamespace, ANamespace::*Test\n-#\n+# ANamespace::AClass, ANamespace::*Test\n+\n # Note that the wildcards are matched against the file with absolute path, so to\n # exclude all test directories use the pattern */test/*\n \n@@ -1164,7 +1361,7 @@ EXAMPLE_RECURSIVE = NO\n \n IMAGE_PATH =\n \n-# The INPUT_FILTER tag can be used to specify a program that doxygen should\n+# The INPUT_FILTER tag can be used to specify a program that Doxygen should\n # invoke to filter for each input file. Doxygen will invoke the filter program\n # by executing (via popen()) the command:\n #\n@@ -1179,9 +1376,14 @@ IMAGE_PATH =\n # code is scanned, but not when the output code is generated. If lines are added\n # or removed, the anchors will not be placed correctly.\n #\n+# Note that Doxygen will use the data processed and written to standard output\n+# for further processing, therefore nothing else, like debug statements or used\n+# commands (so in case of a Windows batch file always use @echo OFF), should be\n+# written to standard output.\n+#\n # Note that for custom extensions or not directly supported extensions you also\n # need to set EXTENSION_MAPPING for the extension otherwise the files are not\n-# properly processed by doxygen.\n+# properly processed by Doxygen.\n \n INPUT_FILTER =\n \n@@ -1194,7 +1396,7 @@ INPUT_FILTER =\n #\n # Note that for custom extensions or not directly supported extensions you also\n # need to set EXTENSION_MAPPING for the extension otherwise the files are not\n-# properly processed by doxygen.\n+# properly processed by Doxygen.\n \n FILTER_PATTERNS =\n \n@@ -1216,10 +1418,28 @@ FILTER_SOURCE_PATTERNS =\n # If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that\n # is part of the input, its contents will be placed on the main page\n # (index.html). This can be useful if you have a project on for instance GitHub\n-# and want to reuse the introduction page also for the doxygen output.\n+# and want to reuse the introduction page also for the Doxygen output.\n \n USE_MDFILE_AS_MAINPAGE =\n \n+# If the IMPLICIT_DIR_DOCS tag is set to YES, any README.md file found in sub-\n+# directories of the project's root, is used as the documentation for that sub-\n+# directory, except when the README.md starts with a \\dir, \\page or \\mainpage\n+# command. If set to NO, the README.md file needs to start with an explicit \\dir\n+# command in order to be used as directory documentation.\n+# The default value is: YES.\n+\n+IMPLICIT_DIR_DOCS = YES\n+\n+# The Fortran standard specifies that for fixed formatted Fortran code all\n+# characters from position 72 are to be considered as comment. A common\n+# extension is to allow longer lines before the automatic comment starts. The\n+# setting FORTRAN_COMMENT_AFTER will also make it possible that longer lines can\n+# be processed before the automatic comment starts.\n+# Minimum value: 7, maximum value: 10000, default value: 72.\n+\n+FORTRAN_COMMENT_AFTER = 72\n+\n #---------------------------------------------------------------------------\n # Configuration options related to source browsing\n #---------------------------------------------------------------------------\n@@ -1234,12 +1454,13 @@ USE_MDFILE_AS_MAINPAGE =\n SOURCE_BROWSER = @do_html@\n \n # Setting the INLINE_SOURCES tag to YES will include the body of functions,\n-# classes and enums directly into the documentation.\n+# multi-line macros, enums or list initialized variables directly into the\n+# documentation.\n # The default value is: NO.\n \n INLINE_SOURCES = NO\n \n-# Setting the STRIP_CODE_COMMENTS tag to YES will instruct doxygen to hide any\n+# Setting the STRIP_CODE_COMMENTS tag to YES will instruct Doxygen to hide any\n # special comment blocks from generated source code fragments. Normal C, C++ and\n # Fortran comments will always remain visible.\n # The default value is: YES.\n@@ -1277,7 +1498,7 @@ REFERENCES_LINK_SOURCE = YES\n SOURCE_TOOLTIPS = YES\n \n # If the USE_HTAGS tag is set to YES then the references to source code will\n-# point to the HTML generated by the htags(1) tool instead of doxygen built-in\n+# point to the HTML generated by the htags(1) tool instead of Doxygen built-in\n # source browser. The htags tool is part of GNU's global source tagging system\n # (see https://www.gnu.org/software/global/global.html). You will need version\n # 4.8.6 or higher.\n@@ -1291,14 +1512,14 @@ SOURCE_TOOLTIPS = YES\n # Doxygen will invoke htags (and that will in turn invoke gtags), so these\n # tools must be available from the command line (i.e. in the search path).\n #\n-# The result: instead of the source browser generated by doxygen, the links to\n+# The result: instead of the source browser generated by Doxygen, the links to\n # source code will now point to the output of htags.\n # The default value is: NO.\n # This tag requires that the tag SOURCE_BROWSER is set to YES.\n \n USE_HTAGS = NO\n \n-# If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a\n+# If the VERBATIM_HEADERS tag is set the YES then Doxygen will generate a\n # verbatim copy of the header file for each class for which an include is\n # specified. Set to NO to disable this.\n # See also: Section \\class.\n@@ -1317,10 +1538,11 @@ VERBATIM_HEADERS = NO\n \n ALPHABETICAL_INDEX = YES\n \n-# In case all classes in a project start with a common prefix, all classes will\n-# be put under the same header in the alphabetical index. The IGNORE_PREFIX tag\n-# can be used to specify a prefix (or a list of prefixes) that should be ignored\n-# while generating the index headers.\n+# The IGNORE_PREFIX tag can be used to specify a prefix (or a list of prefixes)\n+# that should be ignored while generating the index headers. The IGNORE_PREFIX\n+# tag works for classes, function and member names. The entity will be placed in\n+# the alphabetical list under the first letter of the entity name that remains\n+# after removing the prefix.\n # This tag requires that the tag ALPHABETICAL_INDEX is set to YES.\n \n IGNORE_PREFIX =\n@@ -1329,7 +1551,7 @@ IGNORE_PREFIX =\n # Configuration options related to the HTML output\n #---------------------------------------------------------------------------\n \n-# If the GENERATE_HTML tag is set to YES, doxygen will generate HTML output\n+# If the GENERATE_HTML tag is set to YES, Doxygen will generate HTML output\n # The default value is: YES.\n \n GENERATE_HTML = @do_html@\n@@ -1350,40 +1572,40 @@ HTML_OUTPUT = html\n HTML_FILE_EXTENSION = .html\n \n # The HTML_HEADER tag can be used to specify a user-defined HTML header file for\n-# each generated HTML page. If the tag is left blank doxygen will generate a\n+# each generated HTML page. If the tag is left blank Doxygen will generate a\n # standard header.\n #\n # To get valid HTML the header file that includes any scripts and style sheets\n-# that doxygen needs, which is dependent on the configuration options used (e.g.\n+# that Doxygen needs, which is dependent on the configuration options used (e.g.\n # the setting GENERATE_TREEVIEW). It is highly recommended to start with a\n # default header using\n # doxygen -w html new_header.html new_footer.html new_stylesheet.css\n # YourConfigFile\n # and then modify the file new_header.html. See also section \"Doxygen usage\"\n-# for information on how to generate the default header that doxygen normally\n+# for information on how to generate the default header that Doxygen normally\n # uses.\n # Note: The header is subject to change so you typically have to regenerate the\n-# default header when upgrading to a newer version of doxygen. For a description\n+# default header when upgrading to a newer version of Doxygen. For a description\n # of the possible markers and block names see the documentation.\n # This tag requires that the tag GENERATE_HTML is set to YES.\n \n HTML_HEADER =\n \n # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each\n-# generated HTML page. If the tag is left blank doxygen will generate a standard\n+# generated HTML page. If the tag is left blank Doxygen will generate a standard\n # footer. See HTML_HEADER for more information on how to generate a default\n # footer and what special commands can be used inside the footer. See also\n # section \"Doxygen usage\" for information on how to generate the default footer\n-# that doxygen normally uses.\n+# that Doxygen normally uses.\n # This tag requires that the tag GENERATE_HTML is set to YES.\n \n HTML_FOOTER =\n \n # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style\n # sheet that is used by each HTML page. It can be used to fine-tune the look of\n-# the HTML output. If left blank doxygen will generate a default style sheet.\n+# the HTML output. If left blank Doxygen will generate a default style sheet.\n # See also section \"Doxygen usage\" for information on how to generate the style\n-# sheet that doxygen normally uses.\n+# sheet that Doxygen normally uses.\n # Note: It is recommended to use HTML_EXTRA_STYLESHEET instead of this tag, as\n # it is more robust and this tag (HTML_STYLESHEET) will in the future become\n # obsolete.\n@@ -1393,13 +1615,18 @@ HTML_STYLESHEET =\n \n # The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined\n # cascading style sheets that are included after the standard style sheets\n-# created by doxygen. Using this option one can overrule certain style aspects.\n+# created by Doxygen. Using this option one can overrule certain style aspects.\n # This is preferred over using HTML_STYLESHEET since it does not replace the\n # standard style sheet and is therefore more robust against future updates.\n # Doxygen will copy the style sheet files to the output directory.\n # Note: The order of the extra style sheet files is of importance (e.g. the last\n # style sheet in the list overrules the setting of the previous ones in the\n-# list). For an example see the documentation.\n+# list).\n+# Note: Since the styling of scrollbars can currently not be overruled in\n+# Webkit/Chromium, the styling will be left out of the default doxygen.css if\n+# one or more extra stylesheets have been specified. So if scrollbar\n+# customization is desired it has to be added explicitly. For an example see the\n+# documentation.\n # This tag requires that the tag GENERATE_HTML is set to YES.\n \n HTML_EXTRA_STYLESHEET =\n@@ -1414,9 +1641,22 @@ HTML_EXTRA_STYLESHEET =\n \n HTML_EXTRA_FILES =\n \n+# The HTML_COLORSTYLE tag can be used to specify if the generated HTML output\n+# should be rendered with a dark or light theme.\n+# Possible values are: LIGHT always generates light mode output, DARK always\n+# generates dark mode output, AUTO_LIGHT automatically sets the mode according\n+# to the user preference, uses light mode if no preference is set (the default),\n+# AUTO_DARK automatically sets the mode according to the user preference, uses\n+# dark mode if no preference is set and TOGGLE allows a user to switch between\n+# light and dark mode via a button.\n+# The default value is: AUTO_LIGHT.\n+# This tag requires that the tag GENERATE_HTML is set to YES.\n+\n+HTML_COLORSTYLE = AUTO_LIGHT\n+\n # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen\n # will adjust the colors in the style sheet and background images according to\n-# this color. Hue is specified as an angle on a colorwheel, see\n+# this color. Hue is specified as an angle on a color-wheel, see\n # https://en.wikipedia.org/wiki/Hue for more information. For instance the value\n # 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300\n # purple, and 360 is red again.\n@@ -1426,7 +1666,7 @@ HTML_EXTRA_FILES =\n HTML_COLORSTYLE_HUE = 220\n \n # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors\n-# in the HTML output. For a value of 0 the output will use grayscales only. A\n+# in the HTML output. For a value of 0 the output will use gray-scales only. A\n # value of 255 will produce the most vivid colors.\n # Minimum value: 0, maximum value: 255, default value: 100.\n # This tag requires that the tag GENERATE_HTML is set to YES.\n@@ -1444,15 +1684,6 @@ HTML_COLORSTYLE_SAT = 100\n \n HTML_COLORSTYLE_GAMMA = 80\n \n-# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML\n-# page will contain the date and time when the page was generated. Setting this\n-# to YES can help to show when doxygen was last run and thus if the\n-# documentation is up to date.\n-# The default value is: NO.\n-# This tag requires that the tag GENERATE_HTML is set to YES.\n-\n-HTML_TIMESTAMP = NO\n-\n # If the HTML_DYNAMIC_MENUS tag is set to YES then the generated HTML\n # documentation will contain a main index with vertical navigation menus that\n # are dynamically created via JavaScript. If disabled, the navigation index will\n@@ -1472,6 +1703,33 @@ HTML_DYNAMIC_MENUS = YES\n \n HTML_DYNAMIC_SECTIONS = NO\n \n+# If the HTML_CODE_FOLDING tag is set to YES then classes and functions can be\n+# dynamically folded and expanded in the generated HTML source code.\n+# The default value is: YES.\n+# This tag requires that the tag GENERATE_HTML is set to YES.\n+\n+HTML_CODE_FOLDING = YES\n+\n+# If the HTML_COPY_CLIPBOARD tag is set to YES then Doxygen will show an icon in\n+# the top right corner of code and text fragments that allows the user to copy\n+# its content to the clipboard. Note this only works if supported by the browser\n+# and the web page is served via a secure context (see:\n+# https://www.w3.org/TR/secure-contexts/), i.e. using the https: or file:\n+# protocol.\n+# The default value is: YES.\n+# This tag requires that the tag GENERATE_HTML is set to YES.\n+\n+HTML_COPY_CLIPBOARD = YES\n+\n+# Doxygen stores a couple of settings persistently in the browser (via e.g.\n+# cookies). By default these settings apply to all HTML pages generated by\n+# Doxygen across all projects. The HTML_PROJECT_COOKIE tag can be used to store\n+# the settings under a project specific key, such that the user preferences will\n+# be stored separately.\n+# This tag requires that the tag GENERATE_HTML is set to YES.\n+\n+HTML_PROJECT_COOKIE =\n+\n # With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries\n # shown in the various tree structured indices initially; the user can expand\n # and collapse entries dynamically later on. Doxygen will expand the tree to\n@@ -1487,10 +1745,11 @@ HTML_INDEX_NUM_ENTRIES = 0\n \n # If the GENERATE_DOCSET tag is set to YES, additional index files will be\n # generated that can be used as input for Apple's Xcode 3 integrated development\n-# environment (see: https://developer.apple.com/xcode/), introduced with OSX\n-# 10.5 (Leopard). To create a documentation set, doxygen will generate a\n-# Makefile in the HTML output directory. Running make will produce the docset in\n-# that directory and running make install will install the docset in\n+# environment (see:\n+# https://developer.apple.com/xcode/), introduced with OSX 10.5 (Leopard). To\n+# create a documentation set, Doxygen will generate a Makefile in the HTML\n+# output directory. Running make will produce the docset in that directory and\n+# running make install will install the docset in\n # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at\n # startup. See https://developer.apple.com/library/archive/featuredarticles/Doxy\n # genXcode/_index.html for more information.\n@@ -1507,6 +1766,13 @@ GENERATE_DOCSET = NO\n \n DOCSET_FEEDNAME = \"Doxygen generated docs\"\n \n+# This tag determines the URL of the docset feed. A documentation feed provides\n+# an umbrella under which multiple documentation sets from a single provider\n+# (such as a company or product suite) can be grouped.\n+# This tag requires that the tag GENERATE_DOCSET is set to YES.\n+\n+DOCSET_FEEDURL =\n+\n # This tag specifies a string that should uniquely identify the documentation\n # set bundle. This should be a reverse domain-name style string, e.g.\n # com.mycompany.MyDocSet. Doxygen will append .docset to the name.\n@@ -1529,14 +1795,18 @@ DOCSET_PUBLISHER_ID = org.fsf\n \n DOCSET_PUBLISHER_NAME = libstdc++\n \n-# If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three\n+# If the GENERATE_HTMLHELP tag is set to YES then Doxygen generates three\n # additional HTML index files: index.hhp, index.hhc, and index.hhk. The\n # index.hhp is a project file that can be read by Microsoft's HTML Help Workshop\n-# (see: https://www.microsoft.com/en-us/download/details.aspx?id=21138) on\n-# Windows.\n+# on Windows. In the beginning of 2021 Microsoft took the original page, with\n+# a.o. the download links, offline (the HTML help workshop was already many\n+# years in maintenance mode). You can download the HTML help workshop from the\n+# web archives at Installation executable (see:\n+# http://web.archive.org/web/20160201063255/https://download.microsoft.com/downl\n+# oad/0/A/9/0A939EF6-E31C-430F-A3DF-DFAE7960D564/htmlhelp.exe).\n #\n # The HTML Help Workshop contains a compiler that can convert all HTML output\n-# generated by doxygen into a single compiled HTML file (.chm). Compiled HTML\n+# generated by Doxygen into a single compiled HTML file (.chm). Compiled HTML\n # files are now used as the Windows 98 help format, and will replace the old\n # Windows help format (.hlp) on all Windows platforms in the future. Compressed\n # HTML files also contain an index, a table of contents, and you can search for\n@@ -1556,7 +1826,7 @@ CHM_FILE =\n \n # The HHC_LOCATION tag can be used to specify the location (absolute path\n # including file name) of the HTML help compiler (hhc.exe). If non-empty,\n-# doxygen will try to run the HTML help compiler on the generated index.hhp.\n+# Doxygen will try to run the HTML help compiler on the generated index.hhp.\n # The file has to be specified with full path.\n # This tag requires that the tag GENERATE_HTMLHELP is set to YES.\n \n@@ -1590,6 +1860,16 @@ BINARY_TOC = NO\n \n TOC_EXPAND = NO\n \n+# The SITEMAP_URL tag is used to specify the full URL of the place where the\n+# generated documentation will be placed on the server by the user during the\n+# deployment of the documentation. The generated sitemap is called sitemap.xml\n+# and placed on the directory specified by HTML_OUTPUT. In case no SITEMAP_URL\n+# is specified no sitemap is generated. For information about the sitemap\n+# protocol see https://www.sitemaps.org\n+# This tag requires that the tag GENERATE_HTML is set to YES.\n+\n+SITEMAP_URL =\n+\n # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and\n # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that\n # can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help\n@@ -1608,7 +1888,8 @@ QCH_FILE =\n \n # The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help\n # Project output. For more information please see Qt Help Project / Namespace\n-# (see: https://doc.qt.io/archives/qt-4.8/qthelpproject.html#namespace).\n+# (see:\n+# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#namespace).\n # The default value is: org.doxygen.Project.\n # This tag requires that the tag GENERATE_QHP is set to YES.\n \n@@ -1616,7 +1897,8 @@ QHP_NAMESPACE = org.doxygen.Project\n \n # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt\n # Help Project output. For more information please see Qt Help Project / Virtual\n-# Folders (see: https://doc.qt.io/archives/qt-4.8/qthelpproject.html#virtual-folders).\n+# Folders (see:\n+# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#virtual-folders).\n # The default value is: doc.\n # This tag requires that the tag GENERATE_QHP is set to YES.\n \n@@ -1624,14 +1906,16 @@ QHP_VIRTUAL_FOLDER = doc\n \n # If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom\n # filter to add. For more information please see Qt Help Project / Custom\n-# Filters (see: https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters).\n+# Filters (see:\n+# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters).\n # This tag requires that the tag GENERATE_QHP is set to YES.\n \n QHP_CUST_FILTER_NAME =\n \n # The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the\n # custom filter to add. For more information please see Qt Help Project / Custom\n-# Filters (see: https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters).\n+# Filters (see:\n+# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters).\n # This tag requires that the tag GENERATE_QHP is set to YES.\n \n QHP_CUST_FILTER_ATTRS =\n@@ -1643,9 +1927,9 @@ QHP_CUST_FILTER_ATTRS =\n \n QHP_SECT_FILTER_ATTRS =\n \n-# The QHG_LOCATION tag can be used to specify the location of Qt's\n-# qhelpgenerator. If non-empty doxygen will try to run qhelpgenerator on the\n-# generated .qhp file.\n+# The QHG_LOCATION tag can be used to specify the location (absolute path\n+# including file name) of Qt's qhelpgenerator. If non-empty Doxygen will try to\n+# run qhelpgenerator on the generated .qhp file.\n # This tag requires that the tag GENERATE_QHP is set to YES.\n \n QHG_LOCATION =\n@@ -1688,18 +1972,39 @@ DISABLE_INDEX = YES\n # to work a browser that supports JavaScript, DHTML, CSS and frames is required\n # (i.e. any modern browser). Windows users are probably better off using the\n # HTML help feature. Via custom style sheets (see HTML_EXTRA_STYLESHEET) one can\n-# further fine-tune the look of the index. As an example, the default style\n-# sheet generated by doxygen has an example that shows how to put an image at\n-# the root of the tree instead of the PROJECT_NAME. Since the tree basically has\n-# the same information as the tab index, you could consider setting\n-# DISABLE_INDEX to YES when enabling this option.\n-# The default value is: NO.\n+# further fine tune the look of the index (see \"Fine-tuning the output\"). As an\n+# example, the default style sheet generated by Doxygen has an example that\n+# shows how to put an image at the root of the tree instead of the PROJECT_NAME.\n+# Since the tree basically has more details information than the tab index, you\n+# could consider setting DISABLE_INDEX to YES when enabling this option.\n+# The default value is: YES.\n # This tag requires that the tag GENERATE_HTML is set to YES.\n \n GENERATE_TREEVIEW = YES\n \n+# When GENERATE_TREEVIEW is set to YES, the PAGE_OUTLINE_PANEL option determines\n+# if an additional navigation panel is shown at the right hand side of the\n+# screen, displaying an outline of the contents of the main page, similar to\n+# e.g. https://developer.android.com/reference If GENERATE_TREEVIEW is set to\n+# NO, this option has no effect.\n+# The default value is: YES.\n+# This tag requires that the tag GENERATE_HTML is set to YES.\n+\n+PAGE_OUTLINE_PANEL = YES\n+\n+# When GENERATE_TREEVIEW is set to YES, the FULL_SIDEBAR option determines if\n+# the side bar is limited to only the treeview area (value NO) or if it should\n+# extend to the full height of the window (value YES). Setting this to YES gives\n+# a layout similar to e.g. https://docs.readthedocs.io with more room for\n+# contents, but less room for the project logo, title, and description. If\n+# GENERATE_TREEVIEW is set to NO, this option has no effect.\n+# The default value is: NO.\n+# This tag requires that the tag GENERATE_HTML is set to YES.\n+\n+FULL_SIDEBAR = NO\n+\n # The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that\n-# doxygen will group on one line in the generated HTML documentation.\n+# Doxygen will group on one line in the generated HTML documentation.\n #\n # Note that a value of 0 will completely suppress the enum values from appearing\n # in the overview section.\n@@ -1708,6 +2013,12 @@ GENERATE_TREEVIEW = YES\n \n ENUM_VALUES_PER_LINE = 4\n \n+# When the SHOW_ENUM_VALUES tag is set doxygen will show the specified\n+# enumeration values besides the enumeration mnemonics.\n+# The default value is: NO.\n+\n+SHOW_ENUM_VALUES = NO\n+\n # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be used\n # to set the initial width (in pixels) of the frame in which the tree is shown.\n # Minimum value: 0, maximum value: 1500, default value: 250.\n@@ -1715,14 +2026,21 @@ ENUM_VALUES_PER_LINE = 4\n \n TREEVIEW_WIDTH = 250\n \n-# If the EXT_LINKS_IN_WINDOW option is set to YES, doxygen will open links to\n+# If the EXT_LINKS_IN_WINDOW option is set to YES, Doxygen will open links to\n # external symbols imported via tag files in a separate window.\n # The default value is: NO.\n # This tag requires that the tag GENERATE_HTML is set to YES.\n \n EXT_LINKS_IN_WINDOW = NO\n \n-# If the HTML_FORMULA_FORMAT option is set to svg, doxygen will use the pdf2svg\n+# If the OBFUSCATE_EMAILS tag is set to YES, Doxygen will obfuscate email\n+# addresses.\n+# The default value is: YES.\n+# This tag requires that the tag GENERATE_HTML is set to YES.\n+\n+OBFUSCATE_EMAILS = YES\n+\n+# If the HTML_FORMULA_FORMAT option is set to svg, Doxygen will use the pdf2svg\n # tool (see https://github.com/dawbarton/pdf2svg) or inkscape (see\n # https://inkscape.org) to generate formulas as SVG images instead of PNGs for\n # the HTML output. These images will generally look nicer at scaled resolutions.\n@@ -1735,7 +2053,7 @@ HTML_FORMULA_FORMAT = png\n \n # Use this tag to change the font size of LaTeX formulas included as images in\n # the HTML documentation. When you change the font size after a successful\n-# doxygen run you need to manually remove any form_*.png images from the HTML\n+# Doxygen run you need to manually remove any form_*.png images from the HTML\n # output directory to force them to be regenerated.\n # Minimum value: 8, maximum value: 50, default value: 10.\n # This tag requires that the tag GENERATE_HTML is set to YES.\n@@ -1759,50 +2077,90 @@ FORMULA_MACROFILE =\n \n USE_MATHJAX = NO\n \n+# With MATHJAX_VERSION it is possible to specify the MathJax version to be used.\n+# Note that the different versions of MathJax have different requirements with\n+# regards to the different settings, so it is possible that also other MathJax\n+# settings have to be changed when switching between the different MathJax\n+# versions.\n+# Possible values are: MathJax_2, MathJax_3 and MathJax_4.\n+# The default value is: MathJax_2.\n+# This tag requires that the tag USE_MATHJAX is set to YES.\n+\n+MATHJAX_VERSION = MathJax_2\n+\n # When MathJax is enabled you can set the default output format to be used for\n-# the MathJax output. See the MathJax site (see:\n-# http://docs.mathjax.org/en/latest/output.html) for more details.\n+# the MathJax output. For more details about the output format see MathJax\n+# version 2 (see:\n+# https://docs.mathjax.org/en/v2.7/output.html), MathJax version 3 (see:\n+# https://docs.mathjax.org/en/v3.2/output/index.html) and MathJax version 4\n+# (see:\n+# https://docs.mathjax.org/en/v4.0/output/index.htm).\n # Possible values are: HTML-CSS (which is slower, but has the best\n-# compatibility), NativeMML (i.e. MathML) and SVG.\n+# compatibility. This is the name for Mathjax version 2, for MathJax version 3\n+# this will be translated into chtml), NativeMML (i.e. MathML. Only supported\n+# for MathJax 2. For MathJax version 3 chtml will be used instead.), chtml (This\n+# is the name for Mathjax version 3, for MathJax version 2 this will be\n+# translated into HTML-CSS) and SVG.\n # The default value is: HTML-CSS.\n # This tag requires that the tag USE_MATHJAX is set to YES.\n \n MATHJAX_FORMAT = HTML-CSS\n \n # When MathJax is enabled you need to specify the location relative to the HTML\n-# output directory using the MATHJAX_RELPATH option. The destination directory\n-# should contain the MathJax.js script. For instance, if the mathjax directory\n-# is located at the same level as the HTML output directory, then\n-# MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax\n-# Content Delivery Network so you can quickly see the result without installing\n-# MathJax. However, it is strongly recommended to install a local copy of\n-# MathJax from https://www.mathjax.org before deployment.\n-# The default value is: https://cdn.jsdelivr.net/npm/mathjax@2.\n+# output directory using the MATHJAX_RELPATH option. For Mathjax version 2 the\n+# destination directory should contain the MathJax.js script. For instance, if\n+# the mathjax directory is located at the same level as the HTML output\n+# directory, then MATHJAX_RELPATH should be ../mathjax. For Mathjax versions 3\n+# and 4 the destination directory should contain the tex-.js script\n+# (where is either chtml or svg). The default value points to the\n+# MathJax Content Delivery Network so you can quickly see the result without\n+# installing MathJax. However, it is strongly recommended to install a local\n+# copy of MathJax from https://www.mathjax.org before deployment. The default\n+# value is:\n+# - in case of MathJax version 2: https://cdn.jsdelivr.net/npm/mathjax@2\n+# - in case of MathJax version 3: https://cdn.jsdelivr.net/npm/mathjax@3\n+# - in case of MathJax version 4: https://cdn.jsdelivr.net/npm/mathjax@4\n # This tag requires that the tag USE_MATHJAX is set to YES.\n \n MATHJAX_RELPATH = http://www.mathjax.org/mathjax\n \n # The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax\n # extension names that should be enabled during MathJax rendering. For example\n+# for MathJax version 2 (see https://docs.mathjax.org/en/v2.7/tex.html):\n # MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols\n+# For example for MathJax version 3 (see\n+# https://docs.mathjax.org/en/v3.2/input/tex/extensions/):\n+# MATHJAX_EXTENSIONS = ams\n+# For example for MathJax version 4 (see\n+# https://docs.mathjax.org/en/v4.0/input/tex/extensions/):\n+# MATHJAX_EXTENSIONS = units\n+# Note that for Mathjax version 4 quite a few extensions are already\n+# automatically loaded. To disable a package in Mathjax version 4 one can use\n+# the package name prepended with a minus sign (- like MATHJAX_EXTENSIONS +=\n+# -textmacros)\n # This tag requires that the tag USE_MATHJAX is set to YES.\n \n MATHJAX_EXTENSIONS =\n \n-# The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces\n-# of code that will be used on startup of the MathJax code. See the MathJax site\n-# (see: http://docs.mathjax.org/en/latest/output.html) for more details. For an\n-# example see the documentation.\n+# The MATHJAX_CODEFILE tag can be used to specify a file with JavaScript pieces\n+# of code that will be used on startup of the MathJax code. See the Mathjax site\n+# for more details:\n+# - MathJax version 2 (see:\n+# https://docs.mathjax.org/en/v2.7/)\n+# - MathJax version 3 (see:\n+# https://docs.mathjax.org/en/v3.2/)\n+# - MathJax version 4 (see:\n+# https://docs.mathjax.org/en/v4.0/) For an example see the documentation.\n # This tag requires that the tag USE_MATHJAX is set to YES.\n \n MATHJAX_CODEFILE =\n \n-# When the SEARCHENGINE tag is enabled doxygen will generate a search box for\n-# the HTML output. The underlying search engine uses javascript and DHTML and\n+# When the SEARCHENGINE tag is enabled Doxygen will generate a search box for\n+# the HTML output. The underlying search engine uses JavaScript and DHTML and\n # should work on any modern browser. Note that when using HTML help\n # (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET)\n # there is already a search function so this one should typically be disabled.\n-# For large projects the javascript based search engine can be slow, then\n+# For large projects the JavaScript based search engine can be slow, then\n # enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to\n # search using the keyboard; to jump to the search box use + S\n # (what the is depends on the OS and browser, but it is typically\n@@ -1821,7 +2179,7 @@ SEARCHENGINE = NO\n # When the SERVER_BASED_SEARCH tag is enabled the search engine will be\n # implemented using a web server instead of a web client using JavaScript. There\n # are two flavors of web server based searching depending on the EXTERNAL_SEARCH\n-# setting. When disabled, doxygen will generate a PHP script for searching and\n+# setting. When disabled, Doxygen will generate a PHP script for searching and\n # an index file used by the script. When EXTERNAL_SEARCH is enabled the indexing\n # and searching needs to be provided by external tools. See the section\n # \"External Indexing and Searching\" for details.\n@@ -1830,7 +2188,7 @@ SEARCHENGINE = NO\n \n SERVER_BASED_SEARCH = NO\n \n-# When EXTERNAL_SEARCH tag is enabled doxygen will no longer generate the PHP\n+# When EXTERNAL_SEARCH tag is enabled Doxygen will no longer generate the PHP\n # script for searching. Instead the search results are written to an XML file\n # which needs to be processed by an external indexer. Doxygen will invoke an\n # external search engine pointed to by the SEARCHENGINE_URL option to obtain the\n@@ -1838,7 +2196,8 @@ SERVER_BASED_SEARCH = NO\n #\n # Doxygen ships with an example indexer (doxyindexer) and search engine\n # (doxysearch.cgi) which are based on the open source search engine library\n-# Xapian (see: https://xapian.org/).\n+# Xapian (see:\n+# https://xapian.org/).\n #\n # See the section \"External Indexing and Searching\" for details.\n # The default value is: NO.\n@@ -1851,8 +2210,9 @@ EXTERNAL_SEARCH = NO\n #\n # Doxygen ships with an example indexer (doxyindexer) and search engine\n # (doxysearch.cgi) which are based on the open source search engine library\n-# Xapian (see: https://xapian.org/). See the section \"External Indexing and\n-# Searching\" for details.\n+# Xapian (see:\n+# https://xapian.org/). See the section \"External Indexing and Searching\" for\n+# details.\n # This tag requires that the tag SEARCHENGINE is set to YES.\n \n SEARCHENGINE_URL =\n@@ -1873,7 +2233,7 @@ SEARCHDATA_FILE = searchdata.xml\n \n EXTERNAL_SEARCH_ID =\n \n-# The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through doxygen\n+# The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through Doxygen\n # projects other than the one defined by this configuration file, but that are\n # all added to the same external search index. Each project needs to have a\n # unique id set via EXTERNAL_SEARCH_ID. The search mapping then maps the id of\n@@ -1887,7 +2247,7 @@ EXTRA_SEARCH_MAPPINGS =\n # Configuration options related to the LaTeX output\n #---------------------------------------------------------------------------\n \n-# If the GENERATE_LATEX tag is set to YES, doxygen will generate LaTeX output.\n+# If the GENERATE_LATEX tag is set to YES, Doxygen will generate LaTeX output.\n # The default value is: YES.\n \n GENERATE_LATEX = @do_latex@\n@@ -1932,7 +2292,7 @@ MAKEINDEX_CMD_NAME = makeindex\n \n LATEX_MAKEINDEX_CMD = makeindex\n \n-# If the COMPACT_LATEX tag is set to YES, doxygen generates more compact LaTeX\n+# If the COMPACT_LATEX tag is set to YES, Doxygen generates more compact LaTeX\n # documents. This may be useful for small projects and may help to save some\n # trees in general.\n # The default value is: NO.\n@@ -1961,36 +2321,38 @@ PAPER_TYPE = letter\n \n EXTRA_PACKAGES = amsmath\n \n-# The LATEX_HEADER tag can be used to specify a personal LaTeX header for the\n-# generated LaTeX document. The header should contain everything until the first\n-# chapter. If it is left blank doxygen will generate a standard header. See\n-# section \"Doxygen usage\" for information on how to let doxygen write the\n-# default header to a separate file.\n+# The LATEX_HEADER tag can be used to specify a user-defined LaTeX header for\n+# the generated LaTeX document. The header should contain everything until the\n+# first chapter. If it is left blank Doxygen will generate a standard header. It\n+# is highly recommended to start with a default header using\n+# doxygen -w latex new_header.tex new_footer.tex new_stylesheet.sty\n+# and then modify the file new_header.tex. See also section \"Doxygen usage\" for\n+# information on how to generate the default header that Doxygen normally uses.\n #\n-# Note: Only use a user-defined header if you know what you are doing! The\n-# following commands have a special meaning inside the header: $title,\n-# $datetime, $date, $doxygenversion, $projectname, $projectnumber,\n-# $projectbrief, $projectlogo. Doxygen will replace $title with the empty\n-# string, for the replacement values of the other commands the user is referred\n-# to HTML_HEADER.\n+# Note: Only use a user-defined header if you know what you are doing!\n+# Note: The header is subject to change so you typically have to regenerate the\n+# default header when upgrading to a newer version of Doxygen. The following\n+# commands have a special meaning inside the header (and footer): For a\n+# description of the possible markers and block names see the documentation.\n # This tag requires that the tag GENERATE_LATEX is set to YES.\n \n LATEX_HEADER =\n \n-# The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for the\n-# generated LaTeX document. The footer should contain everything after the last\n-# chapter. If it is left blank doxygen will generate a standard footer. See\n+# The LATEX_FOOTER tag can be used to specify a user-defined LaTeX footer for\n+# the generated LaTeX document. The footer should contain everything after the\n+# last chapter. If it is left blank Doxygen will generate a standard footer. See\n # LATEX_HEADER for more information on how to generate a default footer and what\n-# special commands can be used inside the footer.\n-#\n-# Note: Only use a user-defined footer if you know what you are doing!\n+# special commands can be used inside the footer. See also section \"Doxygen\n+# usage\" for information on how to generate the default footer that Doxygen\n+# normally uses. Note: Only use a user-defined footer if you know what you are\n+# doing!\n # This tag requires that the tag GENERATE_LATEX is set to YES.\n \n LATEX_FOOTER =\n \n # The LATEX_EXTRA_STYLESHEET tag can be used to specify additional user-defined\n # LaTeX style sheets that are included after the standard style sheets created\n-# by doxygen. Using this option one can overrule certain style aspects. Doxygen\n+# by Doxygen. Using this option one can overrule certain style aspects. Doxygen\n # will copy the style sheet files to the output directory.\n # Note: The order of the extra style sheet files is of importance (e.g. the last\n # style sheet in the list overrules the setting of the previous ones in the\n@@ -2016,7 +2378,7 @@ LATEX_EXTRA_FILES =\n \n PDF_HYPERLINKS = YES\n \n-# If the USE_PDFLATEX tag is set to YES, doxygen will use the engine as\n+# If the USE_PDFLATEX tag is set to YES, Doxygen will use the engine as\n # specified with LATEX_CMD_NAME to generate the PDF file directly from the LaTeX\n # files. Set this option to YES, to get a higher quality PDF documentation.\n #\n@@ -2026,16 +2388,22 @@ PDF_HYPERLINKS = YES\n \n USE_PDFLATEX = YES\n \n-# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode\n-# command to the generated LaTeX files. This will instruct LaTeX to keep running\n-# if errors occur, instead of asking the user for help. This option is also used\n-# when generating formulas in HTML.\n+# The LATEX_BATCHMODE tag signals the behavior of LaTeX in case of an error.\n+# Possible values are: NO same as ERROR_STOP, YES same as BATCH, BATCH In batch\n+# mode nothing is printed on the terminal, errors are scrolled as if is\n+# hit at every error; missing files that TeX tries to input or request from\n+# keyboard input (\\read on a not open input stream) cause the job to abort,\n+# NON_STOP In nonstop mode the diagnostic message will appear on the terminal,\n+# but there is no possibility of user interaction just like in batch mode,\n+# SCROLL In scroll mode, TeX will stop only for missing files to input or if\n+# keyboard input is necessary and ERROR_STOP In errorstop mode, TeX will stop at\n+# each error, asking for user intervention.\n # The default value is: NO.\n # This tag requires that the tag GENERATE_LATEX is set to YES.\n \n LATEX_BATCHMODE = YES\n \n-# If the LATEX_HIDE_INDICES tag is set to YES then doxygen will not include the\n+# If the LATEX_HIDE_INDICES tag is set to YES then Doxygen will not include the\n # index chapters (such as File Index, Compound Index, etc.) in the output.\n # The default value is: NO.\n # This tag requires that the tag GENERATE_LATEX is set to YES.\n@@ -2045,19 +2413,11 @@ LATEX_HIDE_INDICES = YES\n # The LATEX_BIB_STYLE tag can be used to specify the style to use for the\n # bibliography, e.g. plainnat, or ieeetr. See\n # https://en.wikipedia.org/wiki/BibTeX and \\cite for more info.\n-# The default value is: plain.\n+# The default value is: plainnat.\n # This tag requires that the tag GENERATE_LATEX is set to YES.\n \n LATEX_BIB_STYLE = plain\n \n-# If the LATEX_TIMESTAMP tag is set to YES then the footer of each generated\n-# page will contain the date and time when the page was generated. Setting this\n-# to NO can help when comparing the output of multiple runs.\n-# The default value is: NO.\n-# This tag requires that the tag GENERATE_LATEX is set to YES.\n-\n-LATEX_TIMESTAMP = NO\n-\n # The LATEX_EMOJI_DIRECTORY tag is used to specify the (relative or absolute)\n # path from which the emoji images will be read. If a relative path is entered,\n # it will be relative to the LATEX_OUTPUT directory. If left blank the\n@@ -2070,7 +2430,7 @@ LATEX_EMOJI_DIRECTORY =\n # Configuration options related to the RTF output\n #---------------------------------------------------------------------------\n \n-# If the GENERATE_RTF tag is set to YES, doxygen will generate RTF output. The\n+# If the GENERATE_RTF tag is set to YES, Doxygen will generate RTF output. The\n # RTF output is optimized for Word 97 and may not look too pretty with other RTF\n # readers/editors.\n # The default value is: NO.\n@@ -2085,7 +2445,7 @@ GENERATE_RTF = NO\n \n RTF_OUTPUT = rtf\n \n-# If the COMPACT_RTF tag is set to YES, doxygen generates more compact RTF\n+# If the COMPACT_RTF tag is set to YES, Doxygen generates more compact RTF\n # documents. This may be useful for small projects and may help to save some\n # trees in general.\n # The default value is: NO.\n@@ -2105,28 +2465,36 @@ COMPACT_RTF = NO\n \n RTF_HYPERLINKS = NO\n \n-# Load stylesheet definitions from file. Syntax is similar to doxygen's\n+# Load stylesheet definitions from file. Syntax is similar to Doxygen's\n # configuration file, i.e. a series of assignments. You only have to provide\n # replacements, missing definitions are set to their default value.\n #\n # See also section \"Doxygen usage\" for information on how to generate the\n-# default style sheet that doxygen normally uses.\n+# default style sheet that Doxygen normally uses.\n # This tag requires that the tag GENERATE_RTF is set to YES.\n \n RTF_STYLESHEET_FILE =\n \n # Set optional variables used in the generation of an RTF document. Syntax is\n-# similar to doxygen's configuration file. A template extensions file can be\n+# similar to Doxygen's configuration file. A template extensions file can be\n # generated using doxygen -e rtf extensionFile.\n # This tag requires that the tag GENERATE_RTF is set to YES.\n \n RTF_EXTENSIONS_FILE =\n \n+# The RTF_EXTRA_FILES tag can be used to specify one or more extra images or\n+# other source files which should be copied to the RTF_OUTPUT output directory.\n+# Note that the files will be copied as-is; there are no commands or markers\n+# available.\n+# This tag requires that the tag GENERATE_RTF is set to YES.\n+\n+RTF_EXTRA_FILES =\n+\n #---------------------------------------------------------------------------\n # Configuration options related to the man page output\n #---------------------------------------------------------------------------\n \n-# If the GENERATE_MAN tag is set to YES, doxygen will generate man pages for\n+# If the GENERATE_MAN tag is set to YES, Doxygen will generate man pages for\n # classes and files.\n # The default value is: NO.\n \n@@ -2157,7 +2525,7 @@ MAN_EXTENSION = .3\n \n MAN_SUBDIR =\n \n-# If the MAN_LINKS tag is set to YES and doxygen generates man output, then it\n+# If the MAN_LINKS tag is set to YES and Doxygen generates man output, then it\n # will generate one additional man file for each entity documented in the real\n # man page(s). These additional files only source the real man page, but without\n # them the man command would be unable to find the correct page.\n@@ -2170,7 +2538,7 @@ MAN_LINKS = NO\n # Configuration options related to the XML output\n #---------------------------------------------------------------------------\n \n-# If the GENERATE_XML tag is set to YES, doxygen will generate an XML file that\n+# If the GENERATE_XML tag is set to YES, Doxygen will generate an XML file that\n # captures the structure of the code including all documentation.\n # The default value is: NO.\n \n@@ -2184,7 +2552,7 @@ GENERATE_XML = @do_xml@\n \n XML_OUTPUT = xml\n \n-# If the XML_PROGRAMLISTING tag is set to YES, doxygen will dump the program\n+# If the XML_PROGRAMLISTING tag is set to YES, Doxygen will dump the program\n # listings (including syntax highlighting and cross-referencing information) to\n # the XML output. Note that enabling this will significantly increase the size\n # of the XML output.\n@@ -2193,7 +2561,7 @@ XML_OUTPUT = xml\n \n XML_PROGRAMLISTING = NO\n \n-# If the XML_NS_MEMB_FILE_SCOPE tag is set to YES, doxygen will include\n+# If the XML_NS_MEMB_FILE_SCOPE tag is set to YES, Doxygen will include\n # namespace members in file scope as well, matching the HTML output.\n # The default value is: NO.\n # This tag requires that the tag GENERATE_XML is set to YES.\n@@ -2204,7 +2572,7 @@ XML_NS_MEMB_FILE_SCOPE = NO\n # Configuration options related to the DOCBOOK output\n #---------------------------------------------------------------------------\n \n-# If the GENERATE_DOCBOOK tag is set to YES, doxygen will generate Docbook files\n+# If the GENERATE_DOCBOOK tag is set to YES, Doxygen will generate Docbook files\n # that can be used to generate PDF.\n # The default value is: NO.\n \n@@ -2222,19 +2590,45 @@ DOCBOOK_OUTPUT = docbook\n # Configuration options for the AutoGen Definitions output\n #---------------------------------------------------------------------------\n \n-# If the GENERATE_AUTOGEN_DEF tag is set to YES, doxygen will generate an\n-# AutoGen Definitions (see http://autogen.sourceforge.net/) file that captures\n+# If the GENERATE_AUTOGEN_DEF tag is set to YES, Doxygen will generate an\n+# AutoGen Definitions (see https://autogen.sourceforge.net/) file that captures\n # the structure of the code including all documentation. Note that this feature\n # is still experimental and incomplete at the moment.\n # The default value is: NO.\n \n GENERATE_AUTOGEN_DEF = NO\n \n+#---------------------------------------------------------------------------\n+# Configuration options related to Sqlite3 output\n+#---------------------------------------------------------------------------\n+\n+# If the GENERATE_SQLITE3 tag is set to YES Doxygen will generate a Sqlite3\n+# database with symbols found by Doxygen stored in tables.\n+# The default value is: NO.\n+\n+GENERATE_SQLITE3 = NO\n+\n+# The SQLITE3_OUTPUT tag is used to specify where the Sqlite3 database will be\n+# put. If a relative path is entered the value of OUTPUT_DIRECTORY will be put\n+# in front of it.\n+# The default directory is: sqlite3.\n+# This tag requires that the tag GENERATE_SQLITE3 is set to YES.\n+\n+SQLITE3_OUTPUT = sqlite3\n+\n+# The SQLITE3_RECREATE_DB tag is set to YES, the existing doxygen_sqlite3.db\n+# database file will be recreated with each Doxygen run. If set to NO, Doxygen\n+# will warn if a database file is already found and not modify it.\n+# The default value is: YES.\n+# This tag requires that the tag GENERATE_SQLITE3 is set to YES.\n+\n+SQLITE3_RECREATE_DB = YES\n+\n #---------------------------------------------------------------------------\n # Configuration options related to the Perl module output\n #---------------------------------------------------------------------------\n \n-# If the GENERATE_PERLMOD tag is set to YES, doxygen will generate a Perl module\n+# If the GENERATE_PERLMOD tag is set to YES, Doxygen will generate a Perl module\n # file that captures the structure of the code including all documentation.\n #\n # Note that this feature is still experimental and incomplete at the moment.\n@@ -2242,7 +2636,7 @@ GENERATE_AUTOGEN_DEF = NO\n \n GENERATE_PERLMOD = NO\n \n-# If the PERLMOD_LATEX tag is set to YES, doxygen will generate the necessary\n+# If the PERLMOD_LATEX tag is set to YES, Doxygen will generate the necessary\n # Makefile rules, Perl scripts and LaTeX code to be able to generate PDF and DVI\n # output from the Perl module output.\n # The default value is: NO.\n@@ -2272,13 +2666,13 @@ PERLMOD_MAKEVAR_PREFIX =\n # Configuration options related to the preprocessor\n #---------------------------------------------------------------------------\n \n-# If the ENABLE_PREPROCESSING tag is set to YES, doxygen will evaluate all\n+# If the ENABLE_PREPROCESSING tag is set to YES, Doxygen will evaluate all\n # C-preprocessor directives found in the sources and include files.\n # The default value is: YES.\n \n ENABLE_PREPROCESSING = YES\n \n-# If the MACRO_EXPANSION tag is set to YES, doxygen will expand all macro names\n+# If the MACRO_EXPANSION tag is set to YES, Doxygen will expand all macro names\n # in the source code. If set to NO, only conditional compilation will be\n # performed. Macro expansion can be done in a controlled way by setting\n # EXPAND_ONLY_PREDEF to YES.\n@@ -2304,7 +2698,8 @@ SEARCH_INCLUDES = YES\n \n # The INCLUDE_PATH tag can be used to specify one or more directories that\n # contain include files that are not input files but should be processed by the\n-# preprocessor.\n+# preprocessor. Note that the INCLUDE_PATH is not recursive, so the setting of\n+# RECURSIVE has no effect here.\n # This tag requires that the tag SEARCH_INCLUDES is set to YES.\n \n INCLUDE_PATH = include\n@@ -2429,7 +2824,7 @@ PREDEFINED = __cplusplus=202002L \\\n \n EXPAND_AS_DEFINED =\n \n-# If the SKIP_FUNCTION_MACROS tag is set to YES then doxygen's preprocessor will\n+# If the SKIP_FUNCTION_MACROS tag is set to YES then Doxygen's preprocessor will\n # remove all references to function-like macros that are alone on a line, have\n # an all uppercase name, and do not end with a semicolon. Such function macros\n # are typically used for boiler-plate code, and will confuse the parser if not\n@@ -2453,26 +2848,26 @@ SKIP_FUNCTION_MACROS = YES\n # section \"Linking to external documentation\" for more information about the use\n # of tag files.\n # Note: Each tag file must have a unique name (where the name does NOT include\n-# the path). If a tag file is not located in the directory in which doxygen is\n+# the path). If a tag file is not located in the directory in which Doxygen is\n # run, you must also specify the path to the tagfile here.\n \n TAGFILES =\n \n-# When a file name is specified after GENERATE_TAGFILE, doxygen will create a\n+# When a file name is specified after GENERATE_TAGFILE, Doxygen will create a\n # tag file that is based on the input files it reads. See section \"Linking to\n # external documentation\" for more information about the usage of tag files.\n \n GENERATE_TAGFILE = @generate_tagfile@\n \n-# If the ALLEXTERNALS tag is set to YES, all external class will be listed in\n-# the class index. If set to NO, only the inherited external classes will be\n-# listed.\n+# If the ALLEXTERNALS tag is set to YES, all external classes and namespaces\n+# will be listed in the class and namespace index. If set to NO, only the\n+# inherited external classes will be listed.\n # The default value is: NO.\n \n ALLEXTERNALS = YES\n \n # If the EXTERNAL_GROUPS tag is set to YES, all external groups will be listed\n-# in the modules index. If set to NO, only the current project's groups will be\n+# in the topic index. If set to NO, only the current project's groups will be\n # listed.\n # The default value is: YES.\n \n@@ -2486,73 +2881,111 @@ EXTERNAL_GROUPS = YES\n EXTERNAL_PAGES = YES\n \n #---------------------------------------------------------------------------\n-# Configuration options related to the dot tool\n+# Configuration options related to diagram generator tools\n #---------------------------------------------------------------------------\n \n-# You can include diagrams made with dia in doxygen documentation. Doxygen will\n-# then run dia to produce the diagram and insert it in the documentation. The\n-# DIA_PATH tag allows you to specify the directory where the dia binary resides.\n-# If left empty dia is assumed to be found in the default search path.\n-\n-DIA_PATH =\n-\n # If set to YES the inheritance and collaboration graphs will hide inheritance\n # and usage relations if the target is undocumented or is not a class.\n # The default value is: YES.\n \n HIDE_UNDOC_RELATIONS = NO\n \n-# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is\n+# If you set the HAVE_DOT tag to YES then Doxygen will assume the dot tool is\n # available from the path. This tool is part of Graphviz (see:\n-# http://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent\n+# https://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent\n # Bell Labs. The other options in this section have no effect if this option is\n # set to NO\n # The default value is: NO.\n \n HAVE_DOT = YES\n \n-# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is allowed\n-# to run in parallel. When set to 0 doxygen will base this on the number of\n+# The DOT_NUM_THREADS specifies the number of dot invocations Doxygen is allowed\n+# to run in parallel. When set to 0 Doxygen will base this on the number of\n # processors available in the system. You can set it explicitly to a value\n # larger than 0 to get control over the balance between CPU load and processing\n # speed.\n-# Minimum value: 0, maximum value: 32, default value: 0.\n+# Minimum value: 0, maximum value: 512, default value: 0.\n # This tag requires that the tag HAVE_DOT is set to YES.\n \n DOT_NUM_THREADS = 0\n \n-# By default doxygen will tell dot to use the default font as specified with\n-# DOT_FONTNAME. If you specify a different font using DOT_FONTNAME you can set\n-# the path where dot can find it using this tag.\n+# DOT_COMMON_ATTR is common attributes for nodes, edges and labels of\n+# subgraphs. When you want a differently looking font in the dot files that\n+# Doxygen generates you can specify fontname, fontcolor and fontsize attributes.\n+# For details please see Node,\n+# Edge and Graph Attributes specification You need to make sure dot is able\n+# to find the font, which can be done by putting it in a standard location or by\n+# setting the DOTFONTPATH environment variable or by setting DOT_FONTPATH to the\n+# directory containing the font. Default graphviz fontsize is 14.\n+# The default value is: fontname=Helvetica,fontsize=10.\n+# This tag requires that the tag HAVE_DOT is set to YES.\n+\n+DOT_COMMON_ATTR = \"fontname=Helvetica,fontsize=10\"\n+\n+# DOT_EDGE_ATTR is concatenated with DOT_COMMON_ATTR. For elegant style you can\n+# add 'arrowhead=open, arrowtail=open, arrowsize=0.5'. Complete documentation about\n+# arrows shapes.\n+# The default value is: labelfontname=Helvetica,labelfontsize=10.\n+# This tag requires that the tag HAVE_DOT is set to YES.\n+\n+DOT_EDGE_ATTR = \"labelfontname=Helvetica,labelfontsize=10\"\n+\n+# DOT_NODE_ATTR is concatenated with DOT_COMMON_ATTR. For view without boxes\n+# around nodes set 'shape=plain' or 'shape=plaintext' Shapes specification\n+# The default value is: shape=box,height=0.2,width=0.4.\n+# This tag requires that the tag HAVE_DOT is set to YES.\n+\n+DOT_NODE_ATTR = \"shape=box,height=0.2,width=0.4\"\n+\n+# You can set the path where dot can find font specified with fontname in\n+# DOT_COMMON_ATTR and others dot attributes.\n # This tag requires that the tag HAVE_DOT is set to YES.\n \n DOT_FONTPATH =\n \n-# If the CLASS_GRAPH tag is set to YES then doxygen will generate a graph for\n-# each documented class showing the direct and indirect inheritance relations.\n-# Setting this tag to YES will force the CLASS_DIAGRAMS tag to NO.\n+# If the CLASS_GRAPH tag is set to YES or GRAPH or BUILTIN then Doxygen will\n+# generate a graph for each documented class showing the direct and indirect\n+# inheritance relations. In case the CLASS_GRAPH tag is set to YES or GRAPH and\n+# HAVE_DOT is enabled as well, then dot will be used to draw the graph. In case\n+# the CLASS_GRAPH tag is set to YES and HAVE_DOT is disabled or if the\n+# CLASS_GRAPH tag is set to BUILTIN, then the built-in generator will be used.\n+# If the CLASS_GRAPH tag is set to TEXT the direct and indirect inheritance\n+# relations will be shown as texts / links. Explicit enabling an inheritance\n+# graph or choosing a different representation for an inheritance graph of a\n+# specific class, can be accomplished by means of the command \\inheritancegraph.\n+# Disabling an inheritance graph can be accomplished by means of the command\n+# \\hideinheritancegraph.\n+# Possible values are: NO, YES, TEXT, GRAPH and BUILTIN.\n # The default value is: YES.\n-# This tag requires that the tag HAVE_DOT is set to YES.\n \n CLASS_GRAPH = YES\n \n-# If the COLLABORATION_GRAPH tag is set to YES then doxygen will generate a\n+# If the COLLABORATION_GRAPH tag is set to YES then Doxygen will generate a\n # graph for each documented class showing the direct and indirect implementation\n # dependencies (inheritance, containment, and class references variables) of the\n-# class with other documented classes.\n+# class with other documented classes. Explicit enabling a collaboration graph,\n+# when COLLABORATION_GRAPH is set to NO, can be accomplished by means of the\n+# command \\collaborationgraph. Disabling a collaboration graph can be\n+# accomplished by means of the command \\hidecollaborationgraph.\n # The default value is: YES.\n # This tag requires that the tag HAVE_DOT is set to YES.\n \n COLLABORATION_GRAPH = NO\n \n-# If the GROUP_GRAPHS tag is set to YES then doxygen will generate a graph for\n-# groups, showing the direct groups dependencies.\n+# If the GROUP_GRAPHS tag is set to YES then Doxygen will generate a graph for\n+# groups, showing the direct groups dependencies. Explicit enabling a group\n+# dependency graph, when GROUP_GRAPHS is set to NO, can be accomplished by means\n+# of the command \\groupgraph. Disabling a directory graph can be accomplished by\n+# means of the command \\hidegroupgraph. See also the chapter Grouping in the\n+# manual.\n # The default value is: YES.\n # This tag requires that the tag HAVE_DOT is set to YES.\n \n GROUP_GRAPHS = YES\n \n-# If the UML_LOOK tag is set to YES, doxygen will generate inheritance and\n+# If the UML_LOOK tag is set to YES, Doxygen will generate inheritance and\n # collaboration diagrams in a style similar to the OMG's Unified Modeling\n # Language.\n # The default value is: NO.\n@@ -2569,10 +3002,41 @@ UML_LOOK = NO\n # but if the number exceeds 15, the total amount of fields shown is limited to\n # 10.\n # Minimum value: 0, maximum value: 100, default value: 10.\n-# This tag requires that the tag HAVE_DOT is set to YES.\n+# This tag requires that the tag UML_LOOK is set to YES.\n \n UML_LIMIT_NUM_FIELDS = 10\n \n+# If the UML_LOOK tag is enabled, field labels are shown along the edge between\n+# two class nodes. If there are many fields and many nodes the graph may become\n+# too cluttered. The UML_MAX_EDGE_LABELS threshold limits the number of items to\n+# make the size more manageable. Set this to 0 for no limit.\n+# Minimum value: 0, maximum value: 100, default value: 10.\n+# This tag requires that the tag UML_LOOK is set to YES.\n+\n+UML_MAX_EDGE_LABELS = 10\n+\n+# If the DOT_UML_DETAILS tag is set to NO, Doxygen will show attributes and\n+# methods without types and arguments in the UML graphs. If the DOT_UML_DETAILS\n+# tag is set to YES, Doxygen will add type and arguments for attributes and\n+# methods in the UML graphs. If the DOT_UML_DETAILS tag is set to NONE, Doxygen\n+# will not generate fields with class member information in the UML graphs. The\n+# class diagrams will look similar to the default class diagrams but using UML\n+# notation for the relationships.\n+# Possible values are: NO, YES and NONE.\n+# The default value is: NO.\n+# This tag requires that the tag UML_LOOK is set to YES.\n+\n+DOT_UML_DETAILS = NO\n+\n+# The DOT_WRAP_THRESHOLD tag can be used to set the maximum number of characters\n+# to display on a single line. If the actual line length exceeds this threshold\n+# significantly it will be wrapped across multiple lines. Some heuristics are\n+# applied to avoid ugly line breaks.\n+# Minimum value: 0, maximum value: 1000, default value: 17.\n+# This tag requires that the tag HAVE_DOT is set to YES.\n+\n+DOT_WRAP_THRESHOLD = 17\n+\n # If the TEMPLATE_RELATIONS tag is set to YES then the inheritance and\n # collaboration graphs will show the relations between templates and their\n # instances.\n@@ -2582,24 +3046,29 @@ UML_LIMIT_NUM_FIELDS = 10\n TEMPLATE_RELATIONS = NO\n \n # If the INCLUDE_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are set to\n-# YES then doxygen will generate a graph for each documented file showing the\n+# YES then Doxygen will generate a graph for each documented file showing the\n # direct and indirect include dependencies of the file with other documented\n-# files.\n+# files. Explicit enabling an include graph, when INCLUDE_GRAPH is is set to NO,\n+# can be accomplished by means of the command \\includegraph. Disabling an\n+# include graph can be accomplished by means of the command \\hideincludegraph.\n # The default value is: YES.\n # This tag requires that the tag HAVE_DOT is set to YES.\n \n INCLUDE_GRAPH = NO\n \n # If the INCLUDED_BY_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are\n-# set to YES then doxygen will generate a graph for each documented file showing\n+# set to YES then Doxygen will generate a graph for each documented file showing\n # the direct and indirect include dependencies of the file with other documented\n-# files.\n+# files. Explicit enabling an included by graph, when INCLUDED_BY_GRAPH is set\n+# to NO, can be accomplished by means of the command \\includedbygraph. Disabling\n+# an included by graph can be accomplished by means of the command\n+# \\hideincludedbygraph.\n # The default value is: YES.\n # This tag requires that the tag HAVE_DOT is set to YES.\n \n INCLUDED_BY_GRAPH = NO\n \n-# If the CALL_GRAPH tag is set to YES then doxygen will generate a call\n+# If the CALL_GRAPH tag is set to YES then Doxygen will generate a call\n # dependency graph for every global function or class method.\n #\n # Note that enabling this option will significantly increase the time of a run.\n@@ -2611,7 +3080,7 @@ INCLUDED_BY_GRAPH = NO\n \n CALL_GRAPH = NO\n \n-# If the CALLER_GRAPH tag is set to YES then doxygen will generate a caller\n+# If the CALLER_GRAPH tag is set to YES then Doxygen will generate a caller\n # dependency graph for every global function or class method.\n #\n # Note that enabling this option will significantly increase the time of a run.\n@@ -2623,44 +3092,59 @@ CALL_GRAPH = NO\n \n CALLER_GRAPH = NO\n \n-# If the GRAPHICAL_HIERARCHY tag is set to YES then doxygen will graphical\n+# If the GRAPHICAL_HIERARCHY tag is set to YES then Doxygen will graphical\n # hierarchy of all classes instead of a textual one.\n # The default value is: YES.\n # This tag requires that the tag HAVE_DOT is set to YES.\n \n GRAPHICAL_HIERARCHY = YES\n \n-# If the DIRECTORY_GRAPH tag is set to YES then doxygen will show the\n+# If the DIRECTORY_GRAPH tag is set to YES then Doxygen will show the\n # dependencies a directory has on other directories in a graphical way. The\n # dependency relations are determined by the #include relations between the\n-# files in the directories.\n+# files in the directories. Explicit enabling a directory graph, when\n+# DIRECTORY_GRAPH is set to NO, can be accomplished by means of the command\n+# \\directorygraph. Disabling a directory graph can be accomplished by means of\n+# the command \\hidedirectorygraph.\n # The default value is: YES.\n # This tag requires that the tag HAVE_DOT is set to YES.\n \n DIRECTORY_GRAPH = NO\n \n+# The DIR_GRAPH_MAX_DEPTH tag can be used to limit the maximum number of levels\n+# of child directories generated in directory dependency graphs by dot.\n+# Minimum value: 1, maximum value: 25, default value: 1.\n+# This tag requires that the tag DIRECTORY_GRAPH is set to YES.\n+\n+DIR_GRAPH_MAX_DEPTH = 1\n+\n # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images\n # generated by dot. For an explanation of the image formats see the section\n # output formats in the documentation of the dot tool (Graphviz (see:\n-# http://www.graphviz.org/)).\n-# Note: If you choose svg you need to set HTML_FILE_EXTENSION to xhtml in order\n-# to make the SVG files visible in IE 9+ (other browsers do not have this\n-# requirement).\n+# https://www.graphviz.org/)).\n+#\n+# Note the formats svg:cairo and svg:cairo:cairo cannot be used in combination\n+# with INTERACTIVE_SVG (the INTERACTIVE_SVG will be set to NO).\n # Possible values are: png, jpg, gif, svg, png:gd, png:gd:gd, png:cairo,\n-# png:cairo:gd, png:cairo:cairo, png:cairo:gdiplus, png:gdiplus and\n-# png:gdiplus:gdiplus.\n+# png:cairo:gd, png:cairo:cairo, png:cairo:gdiplus, png:gdiplus,\n+# png:gdiplus:gdiplus, svg:cairo, svg:cairo:cairo, svg:svg, svg:svg:core,\n+# gif:cairo, gif:cairo:gd, gif:cairo:gdiplus, gif:gdiplus, gif:gdiplus:gdiplus,\n+# gif:gd, gif:gd:gd, jpg:cairo, jpg:cairo:gd, jpg:cairo:gdiplus, jpg:gd,\n+# jpg:gd:gd, jpg:gdiplus and jpg:gdiplus:gdiplus.\n # The default value is: png.\n # This tag requires that the tag HAVE_DOT is set to YES.\n \n DOT_IMAGE_FORMAT = svg\n \n-# If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to\n-# enable generation of interactive SVG images that allow zooming and panning.\n+# If DOT_IMAGE_FORMAT is set to svg or svg:svg or svg:svg:core, then this option\n+# can be set to YES to enable generation of interactive SVG images that allow\n+# zooming and panning.\n #\n # Note that this requires a modern browser other than Internet Explorer. Tested\n # and working are Firefox, Chrome, Safari, and Opera.\n-# Note: For IE 9+ you need to set HTML_FILE_EXTENSION to xhtml in order to make\n-# the SVG files visible. Older versions of IE do not have SVG support.\n+#\n+# Note This option will be automatically disabled when DOT_IMAGE_FORMAT is set\n+# to svg:cairo or svg:cairo:cairo.\n # The default value is: NO.\n # This tag requires that the tag HAVE_DOT is set to YES.\n \n@@ -2679,11 +3163,12 @@ DOT_PATH =\n \n DOTFILE_DIRS =\n \n-# The MSCFILE_DIRS tag can be used to specify one or more directories that\n-# contain msc files that are included in the documentation (see the \\mscfile\n-# command).\n+# You can include diagrams made with dia in Doxygen documentation. Doxygen will\n+# then run dia to produce the diagram and insert it in the documentation. The\n+# DIA_PATH tag allows you to specify the directory where the dia binary resides.\n+# If left empty dia is assumed to be found in the default search path.\n \n-MSCFILE_DIRS =\n+DIA_PATH =\n \n # The DIAFILE_DIRS tag can be used to specify one or more directories that\n # contain dia files that are included in the documentation (see the \\diafile\n@@ -2691,28 +3176,85 @@ MSCFILE_DIRS =\n \n DIAFILE_DIRS =\n \n-# When using plantuml, the PLANTUML_JAR_PATH tag should be used to specify the\n-# path where java can find the plantuml.jar file. If left blank, it is assumed\n-# PlantUML is not used or called during a preprocessing step. Doxygen will\n-# generate a warning when it encounters a \\startuml command in this case and\n-# will not generate output for the diagram.\n+# When using PlantUML, the PLANTUML_JAR_PATH tag should be used to specify the\n+# path where java can find the plantuml.jar file or to the filename of jar file\n+# to be used. If left blank, it is assumed PlantUML is not used or called during\n+# a preprocessing step. Doxygen will generate a warning when it encounters a\n+# \\startuml command in this case and will not generate output for the diagram.\n \n PLANTUML_JAR_PATH =\n \n-# When using plantuml, the PLANTUML_CFG_FILE tag can be used to specify a\n-# configuration file for plantuml.\n+# When using PlantUML, the PLANTUML_CFG_FILE tag can be used to specify a\n+# configuration file for PlantUML.\n \n PLANTUML_CFG_FILE =\n \n-# When using plantuml, the specified paths are searched for files specified by\n-# the !include statement in a plantuml block.\n+# When using PlantUML, the specified paths are searched for files specified by\n+# the !include statement in a PlantUML block.\n \n PLANTUML_INCLUDE_PATH =\n \n+# The PLANTUMLFILE_DIRS tag can be used to specify one or more directories that\n+# contain PlantUml files that are included in the documentation (see the\n+# \\plantumlfile command).\n+\n+PLANTUMLFILE_DIRS =\n+\n+# When using Mermaid diagrams with CLI rendering, the MERMAID_PATH tag should be\n+# used to specify the directory where the mmdc (Mermaid CLI) executable can be\n+# found. If left blank, CLI-based rendering is disabled. For HTML output,\n+# client-side rendering via JavaScript is used by default and does not require\n+# mmdc. For LaTeX/PDF output, mmdc is required to pre-generate images. Doxygen\n+# will generate a warning when CLI rendering is needed but mmdc is not\n+# available.\n+\n+MERMAID_PATH =\n+\n+# When using Mermaid diagrams, the MERMAID_CONFIG_FILE tag can be used to\n+# specify a JSON configuration file for the Mermaid CLI tool (mmdc). This file\n+# can contain theme settings and other Mermaid configuration options.\n+\n+MERMAID_CONFIG_FILE =\n+\n+# The MERMAID_RENDER_MODE tag selects how Mermaid diagrams are rendered.\n+# Possible values are: AUTO Use client-side rendering for HTML and mmdc for\n+# LaTeX/PDF and other formats. If MERMAID_PATH is not set, non-HTML diagrams\n+# will produce a warning., CLI Use the mmdc tool to pre-generate images\n+# (requires Node.js and mermaid-js/mermaid-cli). Works for all output formats.\n+# and CLIENT_SIDE Embed mermaid.js in HTML output for client-side rendering.\n+# Does not require mmdc but only works for HTML output..\n+# The default value is: AUTO.\n+\n+MERMAID_RENDER_MODE = AUTO\n+\n+# The MERMAID_JS_URL tag specifies the URL to load mermaid.js from when using\n+# client-side rendering (MERMAID_RENDER_MODE is CLIENT_SIDE or AUTO). The\n+# default points to the latest Mermaid v11 release on the jsDelivr CDN.\n+# Examples:\n+# - Latest v11 (default):\n+# 'https://cdn.jsdelivr.net/npm/mermaid@11/dist/mermaid.esm.min.mjs'\n+# - Pinned version:\n+# 'https://cdn.jsdelivr.net/npm/mermaid@11.3.0/dist/mermaid.esm.min.mjs'\n+# - Local copy: './mermaid.esm.min.mjs' (user must place file in HTML output\n+# directory)\n+# The default CDN URL requires internet access when viewing the generated\n+# documentation. For offline use, download mermaid.esm.min.mjs and set this to a\n+# relative path, or use MERMAID_RENDER_MODE=CLI to pre-generate images instead.\n+# The default value is:\n+# https://cdn.jsdelivr.net/npm/mermaid@11/dist/mermaid.esm.min.mjs.\n+\n+MERMAID_JS_URL = https://cdn.jsdelivr.net/npm/mermaid@11/dist/mermaid.esm.min.mjs\n+\n+# The MERMAIDFILE_DIRS tag can be used to specify one or more directories that\n+# contain Mermaid files that are included in the documentation (see the\n+# \\mermaidfile command).\n+\n+MERMAIDFILE_DIRS =\n+\n # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of nodes\n # that will be shown in the graph. If the number of nodes in a graph becomes\n-# larger than this value, doxygen will truncate the graph, which is visualized\n-# by representing a node as a red box. Note that doxygen if the number of direct\n+# larger than this value, Doxygen will truncate the graph, which is visualized\n+# by representing a node as a red box. Note that if the number of direct\n # children of the root node in a graph is already larger than\n # DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note that\n # the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.\n@@ -2742,17 +3284,37 @@ MAX_DOT_GRAPH_DEPTH = 0\n \n DOT_MULTI_TARGETS = YES\n \n-# If the GENERATE_LEGEND tag is set to YES doxygen will generate a legend page\n+# If the GENERATE_LEGEND tag is set to YES Doxygen will generate a legend page\n # explaining the meaning of the various boxes and arrows in the dot generated\n # graphs.\n+# Note: This tag requires that UML_LOOK isn't set, i.e. the Doxygen internal\n+# graphical representation for inheritance and collaboration diagrams is used.\n # The default value is: YES.\n # This tag requires that the tag HAVE_DOT is set to YES.\n \n GENERATE_LEGEND = YES\n \n-# If the DOT_CLEANUP tag is set to YES, doxygen will remove the intermediate dot\n+# If the DOT_CLEANUP tag is set to YES, Doxygen will remove the intermediate\n # files that are used to generate the various graphs.\n+#\n+# Note: This setting is not only used for dot files but also for msc temporary\n+# files.\n # The default value is: YES.\n-# This tag requires that the tag HAVE_DOT is set to YES.\n \n DOT_CLEANUP = YES\n+\n+# You can define message sequence charts within Doxygen comments using the \\msc\n+# command. If the MSCGEN_TOOL tag is left empty (the default), then Doxygen will\n+# use a built-in version of mscgen tool to produce the charts. Alternatively,\n+# the MSCGEN_TOOL tag can also specify the name an external tool. For instance,\n+# specifying prog as the value, Doxygen will call the tool as prog -T\n+# -o . The external tool should support\n+# output file formats \"png\", \"eps\", \"svg\", and \"ismap\".\n+\n+MSCGEN_TOOL =\n+\n+# The MSCFILE_DIRS tag can be used to specify one or more directories that\n+# contain msc files that are included in the documentation (see the \\mscfile\n+# command).\n+\n+MSCFILE_DIRS =\n","prefixes":["oops/10"]}