My personal C coding style as of late 2023

Re:My personal C coding style as of late 2023 by kristopolous on Monday October 09, 2023 @12:52AM (#37817025)

Speaking of type systems, I read glib as g-lib a few times and tried to understand how you were talking about the GNU lib in that sentence.

[ Parent | on HN ]

Re:My personal C coding style as of late 2023 by zombot on Monday October 09, 2023 @02:28AM (#37817528)

Wouldn't that have to be `glibc`?

[ Parent | on HN ]

Re:My personal C coding style as of late 2023 by slondr on Monday October 09, 2023 @03:08AM (#37817809)

https://en.wikipedia.org/wiki/GLib?wprov=sfti1

[ Parent | on HN ]

Re:My personal C coding style as of late 2023 by zombot on Monday October 09, 2023 @07:41AM (#37819333)

I see. Thanks for that link!

[ Parent | on HN ]

Re:My personal C coding style as of late 2023 by wyldfire on Monday October 09, 2023 @03:47AM (#37818028)

It is unfortunate that the two have such similar names because there's a lot of room for confusion. It doesn't help that they have somewhat adjacent functionality almost.

[ Parent | on HN ]

Re:My personal C coding style as of late 2023 by userbinator on Monday October 09, 2023 @06:08AM (#37818780)

I did too. Humans use context to resolve ambiguities in language, and in this case the context was very much statistically favouring the library; if you're using it, glib is literally "someone else's type system".

[ Parent | on HN ]