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:24:57 +0530 [thread overview]
Message-ID: <CAOM0=dYdLHXY1pN7sz89mWRk39WPCs=6dGkrG70xHKK+5atjsQ@mail.gmail.com> (raw)
In-Reply-To: <3a62e9dd71c1e542e38d6444c955a44185e07936.camel@xry111.site>
On Thu, Nov 17, 2022 at 3:16 PM Xi Ruoyao <xry111@xry111.site> wrote:
>
> On Thu, 2022-11-17 at 12:05 +0530, A via Libc-alpha wrote:
> > Hi,
> >
> > In my opinion, glibc should have support for maps, sets, balanced
> > binary trees, many more string functions, etc. (I know tree and hash
> > are there in glibc), so that developers don't have to implement them
> > themselves, thus saving lots of man hours all over the world.
>
> Because it will save more man hours by implementing them in a separate
> library. You can link the library against any libc (glibc, musl,
> msvcrt, binoic, the libc on Mac OS X - I can't recall the name, ...)
> instead of adding the implementation into all libc implementations.
>
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.
So, implementing a balanced binary tree in 10 - 20 libraries will
consume more man hours than thousands of programmers around the world
trying to implement balanced binary tree in their C projects? I don't
believe this.
> Glibc just contains one implementation of C standard library, it's not
> "the reference implementation": there is just no such a thing in the
> world. The proposal of changing the spec of C language or standard
> library should be sent to WG14, not here.
Hmm...I will see if I can contact them. I searched on Internet but
couldn't figure out who is the right person to contact for this. Do
you know who should I contact?
Amit
next prev parent reply other threads:[~2022-11-17 10:55 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 [this message]
2022-11-17 10:59 ` Xi Ruoyao via Libc-alpha
2022-11-17 11:08 ` A via Libc-alpha
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=dYdLHXY1pN7sz89mWRk39WPCs=6dGkrG70xHKK+5atjsQ@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).