public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r11-8084] libstdc++: Fix even more doxygen markup for group close commands Date: Fri, 9 Apr 2021 12:09:38 +0000 (GMT) [thread overview] Message-ID: <20210409120938.99579398B432@sourceware.org> (raw) https://gcc.gnu.org/g:72ddd861d3881eba141c41c1ccbb4e8b3be159a5 commit r11-8084-g72ddd861d3881eba141c41c1ccbb4e8b3be159a5 Author: Jonathan Wakely <jwakely@redhat.com> Date: Fri Apr 9 00:24:41 2021 +0100 libstdc++: Fix even more doxygen markup for group close commands More fixes like r11-8009 and r11-8066. libstdc++-v3/ChangeLog: * include/bits/fs_fwd.h: Fix doxygen group command. * include/bits/streambuf_iterator.h: Likewise. * include/bits/uses_allocator_args.h: Likewise. * include/std/memory: Likewise. * include/tr1/complex: Likewise. Diff: --- libstdc++-v3/include/bits/fs_fwd.h | 2 +- libstdc++-v3/include/bits/streambuf_iterator.h | 2 +- libstdc++-v3/include/bits/uses_allocator_args.h | 2 +- libstdc++-v3/include/std/memory | 2 +- libstdc++-v3/include/tr1/complex | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/libstdc++-v3/include/bits/fs_fwd.h b/libstdc++-v3/include/bits/fs_fwd.h index 1b9c388ef8c..3a1ff35f8e2 100644 --- a/libstdc++-v3/include/bits/fs_fwd.h +++ b/libstdc++-v3/include/bits/fs_fwd.h @@ -339,7 +339,7 @@ _GLIBCXX_END_NAMESPACE_CXX11 bool is_symlink(file_status) noexcept; } // namespace filesystem -// @} +/// @} _GLIBCXX_END_NAMESPACE_VERSION } // namespace std #endif // C++17 diff --git a/libstdc++-v3/include/bits/streambuf_iterator.h b/libstdc++-v3/include/bits/streambuf_iterator.h index 22af3fd5995..cda596af40f 100644 --- a/libstdc++-v3/include/bits/streambuf_iterator.h +++ b/libstdc++-v3/include/bits/streambuf_iterator.h @@ -498,7 +498,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION __i._M_c = __eof; } -// @} group iterators +/// @} group iterators _GLIBCXX_END_NAMESPACE_VERSION } // namespace diff --git a/libstdc++-v3/include/bits/uses_allocator_args.h b/libstdc++-v3/include/bits/uses_allocator_args.h index 8b95e8087a2..8b548ff6981 100644 --- a/libstdc++-v3/include/bits/uses_allocator_args.h +++ b/libstdc++-v3/include/bits/uses_allocator_args.h @@ -220,7 +220,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION }, std::uses_allocator_construction_args<_Tp>(__a, std::forward<_Args>(__args)...)); } -// @} +/// @} _GLIBCXX_END_NAMESPACE_VERSION } // namespace std #endif // C++20 diff --git a/libstdc++-v3/include/std/memory b/libstdc++-v3/include/std/memory index f077e7c8bf1..f19de275b2b 100644 --- a/libstdc++-v3/include/std/memory +++ b/libstdc++-v3/include/std/memory @@ -128,7 +128,7 @@ undeclare_no_pointers(char*, size_t) { } /// The type of pointer safety supported by the implementation. inline pointer_safety get_pointer_safety() noexcept { return pointer_safety::relaxed; } -// @} +/// @} _GLIBCXX_END_NAMESPACE_VERSION } // namespace diff --git a/libstdc++-v3/include/tr1/complex b/libstdc++-v3/include/tr1/complex index 2440c742fad..6b04ca32f77 100644 --- a/libstdc++-v3/include/tr1/complex +++ b/libstdc++-v3/include/tr1/complex @@ -411,7 +411,7 @@ namespace tr1 pow(const std::complex<_Tp>& __x, const std::complex<_Tp>& __y) { return std::pow(__x, __y); } -// @} group complex_numbers +/// @} group complex_numbers } _GLIBCXX_END_NAMESPACE_VERSION
reply other threads:[~2021-04-09 12:09 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20210409120938.99579398B432@sourceware.org \ --to=redi@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-cvs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).