From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 2181) id 5CBEB38582A7; Wed, 21 Sep 2022 07:45:26 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5CBEB38582A7 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1663746326; bh=lN8u2FdIOd4VR4Tfdk7NC9XVEI/ElLyI3gh7DSo35zA=; h=From:To:Subject:Date:From; b=MlQz9JJ2AA1PMqSN8D603P661YkuD5iO4OgCtQMRirJHZQebR29I3Mzl3eEKzBMmi pmLQeJ0+NrHZbGgSgNBAdTorK0r403TCfkMbf+aSg6i+1K7Um65MoBkmsswN9Xh718 TPmznhfxnHY3GlJM9+gDGUfTR3FW8ugTmGjSADIY= 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 r13-2753] libstdc++: Remove trailing whitespace in documentation sources X-Act-Checkin: gcc X-Git-Author: Jonathan Wakely X-Git-Refname: refs/heads/master X-Git-Oldrev: cb29396e67f5e2622e31bf83f253c6d66c51135d X-Git-Newrev: 9c23fe08c1fcee524503b24e15321b20df136f6c Message-Id: <20220921074526.5CBEB38582A7@sourceware.org> Date: Wed, 21 Sep 2022 07:45:26 +0000 (GMT) List-Id: https://gcc.gnu.org/g:9c23fe08c1fcee524503b24e15321b20df136f6c commit r13-2753-g9c23fe08c1fcee524503b24e15321b20df136f6c Author: Jonathan Wakely Date: Wed Sep 21 01:18:38 2022 +0100 libstdc++: Remove trailing whitespace in documentation sources libstdc++-v3/ChangeLog: * doc/xml/manual/documentation_hacking.xml: Remove trailing whitespace. * doc/xml/manual/policy_data_structures.xml: Likewise. Diff: --- libstdc++-v3/doc/xml/manual/documentation_hacking.xml | 4 ++-- libstdc++-v3/doc/xml/manual/policy_data_structures.xml | 12 ++++++------ 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/libstdc++-v3/doc/xml/manual/documentation_hacking.xml b/libstdc++-v3/doc/xml/manual/documentation_hacking.xml index 03bf1f184d4..776d5e857b5 100644 --- a/libstdc++-v3/doc/xml/manual/documentation_hacking.xml +++ b/libstdc++-v3/doc/xml/manual/documentation_hacking.xml @@ -353,7 +353,7 @@ documentation. Here are some of the obvious errors, and ways to fix some common issues that may appear quite cryptic. - + First, if using a rule like make pdf, try to narrow down the scope of the error to either docbook @@ -844,7 +844,7 @@ make XSL_STYLE_DIR="/usr/share/xml/docbook/stylesheet/nwalsh" documentation. Here are some of the obvious errors, and ways to fix some common issues that may appear quite cryptic. - + First, if using a rule like make pdf, try to narrow down the scope of the error to either docbook diff --git a/libstdc++-v3/doc/xml/manual/policy_data_structures.xml b/libstdc++-v3/doc/xml/manual/policy_data_structures.xml index 3e598105f7e..305257c7404 100644 --- a/libstdc++-v3/doc/xml/manual/policy_data_structures.xml +++ b/libstdc++-v3/doc/xml/manual/policy_data_structures.xml @@ -3003,7 +3003,7 @@ - + Let U be a domain (e.g., the integers, or the strings of 3 characters). A hash-table algorithm needs to map elements of U "uniformly" into the range [0,..., m - @@ -3179,7 +3179,7 @@ 0t - 1 si ai mod m - + where a is some non-negative integral value. This is the standard string-hashing function used in SGI's @@ -3278,7 +3278,7 @@ - + If cc_hash_table's hash-functor, Hash_Fn is instantiated by null_type , then Comb_Hash_Fn is taken to be a ranged-hash function. The graphic below shows an insert sequence @@ -3298,7 +3298,7 @@ - +
@@ -3917,7 +3917,7 @@ - + Supporting such trees is difficult for a number of reasons: @@ -4819,7 +4819,7 @@ assert(p.top() == 3); - + It should be noted that an alternative design could embed an associative container in a priority queue. Could, but most probably should not. To begin with, it should be noted that one