Re: GNU/Linux is the Empowerment of the PC. So What Do You Do?

vallor wrote this copyrighted missive and expects royalties:

On Fri, 12 Apr 2024 15:16:26 -0400, Chris Ahlstrom <OFeem1987@teleworm.us>
wrote in <uvc1aa$2h40t$1@dont-email.me>:
>

rbowman wrote this copyrighted missive and expects royalties:
 

On Fri, 12 Apr 2024 12:23:37 -0400, DFS wrote:
>

It's common knowledge MS used the BSD FOSS TCP/IP code, but they wrote
their own brand new implementation 16 frickin' years ago.  That's
sixteen.

>
And winsock.h  still is a little strange.

 
All windows headers are bloated monstrosities. Ya better just include
the massive universe of <windows.h> :-D

>
That doesn't sound very POSIX, but I might be biased (see domain name).
>

On the other hand, GNU code is full of IFs ANDs BUTs and MAYBEs.
 
Jesus the gettext headers and code are ... obtuse.

>
But how often do you have to go into those?  Don't you just enable
a feature macro and Bob's your uncle?

I want to parse .mo files without using the GNU API for that.
First you have to figure out what the code does. There's the rub.

Let's say you want to figure out how a function like ngettext() works.
You find two files: intl/ngettext.c and src/ngettext.c.

In the first one, #ifdef _LIBC then NGETTEXT is defiend as __ngettext,
otherwise it is defined as libintl_ngettext. Then

GETTEXT (const char *msgid1, const char *msgid2, unsigned long int n)
{
      return DCNGETTEXT (NULL, msgid1, msgid2, n, LC_MESSAGES);
}

where DCNGETTEXT is defined as __dcngettext or libintl_dcngettext.

Also __ngettext is a "weak_alias" for ngettext, or maybe vice versa.

Now we look in intl/dcngettext.c and find macros similar to the above.
And then

DCNGETTEXT (const char *domainname,
        const char *msgid1, const char *msgid2, unsigned long int n,
                int category)
{
      return DCIGETTEXT (domainname, msgid1, msgid2, 1, n, category);
}

At this point I want to kick Ulrich Drepper's ass!

In dcigettext.c we find more macros and finally the dcigettext() function.
It's chock full of conditional macros, uses some lock/unlock code and
indirection galore. About 460 lines of crappily-indented code. Supported
by a number of other functions loaded with pointer arguments, including another
400+ liner.

You bet your roots toots it's tons of fun!

--
Avoid reality at all costs.