From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 2181) id CA287385840B; Tue, 30 Nov 2021 13:10:16 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CA287385840B MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" From: Jonathan Wakely To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r12-5624] libstdc++: Use gender-agnostic pronoun in docs X-Act-Checkin: gcc X-Git-Author: Jonathan Wakely X-Git-Refname: refs/heads/master X-Git-Oldrev: 92084a6dcda8aaee538b4512bbaf161e1155a296 X-Git-Newrev: 67013a2f711d3df6362972d53cd82da86a170162 Message-Id: <20211130131016.CA287385840B@sourceware.org> Date: Tue, 30 Nov 2021 13:10:16 +0000 (GMT) X-BeenThere: libstdc++-cvs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libstdc++-cvs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2021 13:10:16 -0000 https://gcc.gnu.org/g:67013a2f711d3df6362972d53cd82da86a170162 commit r12-5624-g67013a2f711d3df6362972d53cd82da86a170162 Author: Jonathan Wakely Date: Tue Nov 30 13:05:08 2021 +0000 libstdc++: Use gender-agnostic pronoun in docs libstdc++-v3/ChangeLog: * doc/xml/manual/debug_mode.xml: Replace "his or her" with "they". * doc/html/manual/debug_mode_design.html: Regenerate. Diff: --- libstdc++-v3/doc/html/manual/debug_mode_design.html | 10 +++++----- libstdc++-v3/doc/xml/manual/debug_mode.xml | 10 +++++----- 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/libstdc++-v3/doc/html/manual/debug_mode_design.html b/libstdc++-v3/doc/html/manual/debug_mode_design.html index 671e8dbb814..03f72ae96fe 100644 --- a/libstdc++-v3/doc/html/manual/debug_mode_design.html +++ b/libstdc++-v3/doc/html/manual/debug_mode_design.html @@ -38,25 +38,25 @@ higher-numbered conformance levels are more usable (i.e., require less recompilation) but are more complicated to implement than the lower-numbered conformance levels. -

  1. Full recompilation: The user must recompile his or - her entire application and all C++ libraries it depends on, +

    1. Full recompilation: The user must recompile + their entire application and all C++ libraries it depends on, including the C++ standard library that ships with the compiler. This must be done even if only a small part of the program can use debugging features.

    2. Full user recompilation: The user must recompile - his or her entire application and all C++ libraries it depends + their entire application and all C++ libraries it depends on, but not the C++ standard library itself. This must be done even if only a small part of the program can use debugging features. This can be achieved given a full recompilation system by compiling two versions of the standard library when the compiler is installed and linking against the appropriate one, e.g., a multilibs approach.

    3. Partial recompilation: The user must recompile the - parts of his or her application and the C++ libraries it + parts of their application and the C++ libraries it depends on that will use the debugging facilities directly. This means that any code that uses the debuggable standard containers would need to be recompiled, but code that does not use them (but may, for instance, use IOStreams) would not have to be recompiled.

    4. Per-use recompilation: The user must recompile the - parts of his or her application and the C++ libraries it + parts of their application and the C++ libraries it depends on where debugging should occur, and any other code that interacts with those containers. This means that a set of translation units that accesses a particular standard diff --git a/libstdc++-v3/doc/xml/manual/debug_mode.xml b/libstdc++-v3/doc/xml/manual/debug_mode.xml index dbd5c2b7775..988c4a93601 100644 --- a/libstdc++-v3/doc/xml/manual/debug_mode.xml +++ b/libstdc++-v3/doc/xml/manual/debug_mode.xml @@ -393,14 +393,14 @@ That alias is deprecated and may be removed in a future release. less recompilation) but are more complicated to implement than the lower-numbered conformance levels. - Full recompilation: The user must recompile his or - her entire application and all C++ libraries it depends on, + Full recompilation: The user must recompile + their entire application and all C++ libraries it depends on, including the C++ standard library that ships with the compiler. This must be done even if only a small part of the program can use debugging features. Full user recompilation: The user must recompile - his or her entire application and all C++ libraries it depends + their entire application and all C++ libraries it depends on, but not the C++ standard library itself. This must be done even if only a small part of the program can use debugging features. This can be achieved given a full recompilation @@ -409,7 +409,7 @@ That alias is deprecated and may be removed in a future release. one, e.g., a multilibs approach. Partial recompilation: The user must recompile the - parts of his or her application and the C++ libraries it + parts of their application and the C++ libraries it depends on that will use the debugging facilities directly. This means that any code that uses the debuggable standard containers would need to be recompiled, but code @@ -417,7 +417,7 @@ That alias is deprecated and may be removed in a future release. would not have to be recompiled. Per-use recompilation: The user must recompile the - parts of his or her application and the C++ libraries it + parts of their application and the C++ libraries it depends on where debugging should occur, and any other code that interacts with those containers. This means that a set of translation units that accesses a particular standard