From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: libc-alpha@sourceware.org
Subject: [PATCH] [patchwork-test] Make glibc into a C++ library
Date: Thu, 30 Apr 2020 07:45:23 +0530 [thread overview]
Message-ID: <20200430021523.97495-1-siddhesh@sourceware.org> (raw)
C is for old people and C++ is the future. Start by changing the
README, we can get to changing the library later.
---
README | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/README b/README
index 31c5da0405..f2669be72f 100644
--- a/README
+++ b/README
@@ -1,7 +1,7 @@
-This directory contains the sources of the GNU C Library.
+This directory contains the sources of the GNU C++ Library.
See the file "version.h" for what release version you have.
-The GNU C Library is the standard system C library for all GNU systems,
+The GNU C++ Library is the standard system C library for all GNU systems,
and is an important part of what makes up a GNU system. It provides the
system API for all programs written in C and C-compatible languages such
as C++ and Objective C; the runtime facilities of other programming
@@ -11,16 +11,16 @@ In GNU/Linux systems, the C library works with the Linux kernel to
implement the operating system behavior seen by user applications.
In GNU/Hurd systems, it works with a microkernel and Hurd servers.
-The GNU C Library implements much of the POSIX.1 functionality in the
+The GNU C++ Library implements much of the POSIX.1 functionality in the
GNU/Hurd system, using configurations i[4567]86-*-gnu.
-When working with Linux kernels, this version of the GNU C Library
+When working with Linux kernels, this version of the GNU C++ Library
requires Linux kernel version 3.2 or later.
Also note that the shared version of the libgcc_s library must be
installed for the pthread library to work correctly.
-The GNU C Library supports these configurations for using Linux kernels:
+The GNU C++ Library supports these configurations for using Linux kernels:
aarch64*-*-linux-gnu
alpha*-*-linux-gnu
@@ -48,10 +48,10 @@ maintainers; see https://www.gnu.org/software/libc/ for more
information.
See the file INSTALL to find out how to configure, build, and install
-the GNU C Library. You might also consider reading the WWW pages for
+the GNU C++ Library. You might also consider reading the WWW pages for
the C library at https://www.gnu.org/software/libc/.
-The GNU C Library is (almost) completely documented by the Texinfo manual
+The GNU C++ Library is (almost) completely documented by the Texinfo manual
found in the `manual/' subdirectory. The manual is still being updated
and contains some known errors and omissions; we regret that we do not
have the resources to work on the manual as much as we would like. For
@@ -64,7 +64,7 @@ Please see https://www.gnu.org/software/libc/bugs.html for bug reporting
information. We are now using the Bugzilla system to track all bug reports.
This web page gives detailed information on how to report bugs properly.
-The GNU C Library is free software. See the file COPYING.LIB for copying
+The GNU C++ Library is free software. See the file COPYING.LIB for copying
conditions, and LICENSES for notices about a few contributions that require
these additional notices to be distributed. License copyright years may be
listed using range notation, e.g., 1996-2015, indicating that every year in
--
2.25.3
next reply other threads:[~2020-04-30 2:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 2:15 Siddhesh Poyarekar [this message]
2020-04-30 2:18 ` Siddhesh Poyarekar
2020-04-30 2:39 ` Siddhesh Poyarekar
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=20200430021523.97495-1-siddhesh@sourceware.org \
--to=siddhesh@sourceware.org \
--cc=libc-alpha@sourceware.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).