My personal C coding style as of late 2023

Re:My personal C coding style as of late 2023 by badsectoracula on Sunday October 08, 2023 @10:01PM (#37816184)

> I might just be a grumpy old dev [...] Everyone knows what a uint32_t is when they see it.

You might not be old enough then :-P many codebases typedef their own int types. See glib (gint, gshort, gint32, etc), SDL (Sint32, Uint32, etc) off the top of my head and there are many that define types like "int32" or "i32" like the linked article.

[ Parent | on HN ]

Re:My personal C coding style as of late 2023 by ComputerGuru on Sunday October 08, 2023 @10:57PM (#37816493)

I cut my teeth on DWORD, PHALF_PTR, and friends, so my issue is not so much “don’t know how to grok this” as it is “we finally have sane, universal type names and you’re throwing them away.”

Sure, the _t suffix may be an eyesore but I’ll take size_t over “size” any day.

[ Parent | on HN ]

Re:My personal C coding style as of late 2023 by LoganDark on Sunday October 08, 2023 @11:39PM (#37816701)

I like Rust's approach of "isize", as in "size" is in the place of the bit width. "size" sounds stupid.

[ Parent | on HN ]