public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-1109] c++: Use better module partition naming
Date: Wed, 15 Jun 2022 15:03:09 +0000 (GMT)	[thread overview]
Message-ID: <20220615150309.99A9F3858D32@sourceware.org> (raw)

https://gcc.gnu.org/g:052d89537a4c09e1e1437042e2d1ea215656325f

commit r13-1109-g052d89537a4c09e1e1437042e2d1ea215656325f
Author: Nathan Sidwell <nathan@acm.org>
Date:   Fri Jun 10 11:57:38 2022 -0700

    c++: Use better module partition naming
    
    It turns out that 'implementation partition' is not a term used in the
    std, and is confusing to users.  Let's use the better term 'internal
    partition'.  While there, adjust header unit naming.
    
            gcc/cp/
            * module.cc (module_state::write_readme): Use less confusing
            importable unit names.

Diff:
---
 gcc/cp/module.cc | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/gcc/cp/module.cc b/gcc/cp/module.cc
index 5566c49490f..b3fbd467ecb 100644
--- a/gcc/cp/module.cc
+++ b/gcc/cp/module.cc
@@ -13962,11 +13962,11 @@ module_state::write_readme (elf_out *to, cpp_reader *reader, const char *dialect
 
   readme.begin (false);
 
-  readme.printf ("GNU C++ %smodule%s%s",
-		 is_header () ? "header " : is_partition () ? "" : "primary ",
-		 is_header () ? ""
-		 : is_interface () ? " interface" : " implementation",
-		 is_partition () ? " partition" : "");
+  readme.printf ("GNU C++ %s",
+		 is_header () ? "header unit"
+		 : !is_partition () ? "primary interface"
+		 : is_interface () ? "interface partition"
+		 : "internal partition");
 
   /* Compiler's version.  */
   readme.printf ("compiler: %s", version_string);


                 reply	other threads:[~2022-06-15 15:03 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=20220615150309.99A9F3858D32@sourceware.org \
    --to=nathan@gcc.gnu.org \
    --cc=gcc-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: link
Be 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).