TeamHeptaMirrors/gcc
1
0
Fork 1
mirror of https://github.com/gcc-mirror/gcc.git synced 2026-05-06 14:59:39 +02:00
Code Issues Packages Projects Releases Wiki Activity

libstdc++: Replace "_N" in examples of naming conventions

Browse Source 
The name "_N" is listed as a reserved name on Solaris, so we shouldn't
use it as an example of our naming conventions.

libstdc++-v3/ChangeLog:

	* doc/xml/manual/appendix_contributing.xml: Replace example that
	uses a BADNAME.
	* doc/html/manual/source_code_style.html: Regenerate.
This commit is contained in:
Jonathan Wakely
2023-11-03 12:30:59 +00:00
parent 8067caa85d
commit 6933c05ade
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
libstdc++-v3/doc/html/manual/source_code_style.html
View File

@@ -468,7 +468,7 @@
<br />
      Type names and template formal-argument names: <code class="literal">_[A-Z][^_].*</code><br />
<br />
      Examples:  <code class="code">_Helper  _CharT  _N</code><br />
      Examples:  <code class="code">_Helper  _CharT  _Nm</code><br />
<br />
      Member data and function names: <code class="literal">_M_.*</code><br />
<br />
@@ -480,7 +480,7 @@
<br />
      Don't use names in the same scope that differ only in the prefix,<br />
      e.g. _S_top and _M_top. See <a class="link" href="source_code_style.html#coding_style.bad_identifiers" title="Bad Identifiers">BADNAMES</a> for a list of forbidden names.<br />
      (The most tempting of these seem to be and "_T" and "__sz".)<br />
      (The most tempting of these seem to be and "_T" and "_N".)<br />
<br />
      Names must never have "__" internally; it would confuse name<br />
      unmanglers on some targets. Also, never use "__[0-9]", same reason.<br />

4
libstdc++-v3/doc/xml/manual/appendix_contributing.xml
View File

@@ -887,7 +887,7 @@ indicate a place that may require attention for multi-thread safety.
Type names and template formal-argument names: <literal>_[A-Z][^_].*</literal>
Examples: <code>_Helper _CharT _N</code>
Examples: <code>_Helper _CharT _Nm</code>
Member data and function names: <literal>_M_.*</literal>
@@ -899,7 +899,7 @@ indicate a place that may require attention for multi-thread safety.
Don't use names in the same scope that differ only in the prefix,
e.g. _S_top and _M_top. See <link linkend="coding_style.bad_identifiers">BADNAMES</link> for a list of forbidden names.
(The most tempting of these seem to be and "_T" and "__sz".)
(The most tempting of these seem to be and "_T" and "_N".)
Names must never have "__" internally; it would confuse name
unmanglers on some targets. Also, never use "__[0-9]", same reason.