From: Xi Ruoyao <xry111@xry111.site>
To: A <amit234234234234@gmail.com>
Cc: libc-alpha@sourceware.org
Subject: Re: Why is glibc not extensive?
Date: Thu, 17 Nov 2022 18:59:31 +0800 [thread overview]
Message-ID: <e69c0ed5f35ee94180230bef52c49b803525219e.camel@xry111.site> (raw)
In-Reply-To: <CAOM0=dYdLHXY1pN7sz89mWRk39WPCs=6dGkrG70xHKK+5atjsQ@mail.gmail.com>
On Thu, 2022-11-17 at 16:24 +0530, A wrote:
> 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.
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.
> 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.
It will consume more man hours than implementing a balanced binary tree
as a separate library and link all these projects to the library.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2022-11-17 10:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 6:35 A
2022-11-17 9:46 ` Xi Ruoyao
2022-11-17 10:54 ` A
2022-11-17 10:59 ` Xi Ruoyao [this message]
2022-11-17 11:08 ` A
2022-11-17 11:13 ` Xi Ruoyao
2022-11-17 11:19 ` Xi Ruoyao
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=e69c0ed5f35ee94180230bef52c49b803525219e.camel@xry111.site \
--to=xry111@xry111.site \
--cc=amit234234234234@gmail.com \
--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).