From: A via Libc-alpha <libc-alpha@sourceware.org>
To: Xi Ruoyao <xry111@xry111.site>
Cc: libc-alpha@sourceware.org
Subject: Re: Why is glibc not extensive?
Date: Thu, 17 Nov 2022 16:38:36 +0530 [thread overview]
Message-ID: <CAOM0=dYhix5PkBoa8KSEu_hEWK2MDN409-RvAGZsb5WD07yqXQ@mail.gmail.com> (raw)
In-Reply-To: <e69c0ed5f35ee94180230bef52c49b803525219e.camel@xry111.site>
On Thu, Nov 17, 2022 at 4:29 PM Xi Ruoyao <xry111@xry111.site> wrote:
>
> On Thu, 2022-11-17 at 16:24 +0530, A wrote:
> > So, do glibc developers also take care of musl, msvcrt, etc.? I didn't
> > know this. And if not, then why would glibc developers bother about
> > other libc implementations.
>
> Because if the fancy features are supported by Glibc but not other libc
> implementations, the programmers will likely re-implement the feature
> anyway because they want there program functional with different libc
> implementations.
They will not implement again. They will copy from glibc.Currently,
everyone is implementing their own and using lots of man hours.
Copying is 5 minutes job.
Amit
next prev parent reply other threads:[~2022-11-17 11:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 6:35 Why is glibc not extensive? A via Libc-alpha
2022-11-17 9:46 ` Xi Ruoyao via Libc-alpha
2022-11-17 10:54 ` A via Libc-alpha
2022-11-17 10:59 ` Xi Ruoyao via Libc-alpha
2022-11-17 11:08 ` A via Libc-alpha [this message]
2022-11-17 11:13 ` Xi Ruoyao via Libc-alpha
2022-11-17 11:19 ` Xi Ruoyao via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOM0=dYhix5PkBoa8KSEu_hEWK2MDN409-RvAGZsb5WD07yqXQ@mail.gmail.com' \
--to=libc-alpha@sourceware.org \
--cc=amit234234234234@gmail.com \
--cc=xry111@xry111.site \
/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).