Re:My personal C coding style as of late 2023
by uxp8u61q on Monday October 09, 2023 @08:52AM
(#37819943)
Long type name?? uint32_t is literally 8 characters long. There's not much to cut here.
[ Parent
| on HN ]
Re:My personal C coding style as of late 2023
by slikrick on Monday October 09, 2023 @09:30AM
(#37820282)
if you like typing _, go ahead, but it's not 1 key press and shouldn't be treated as a keystroke like the letter a...
Re:My personal C coding style as of late 2023
by uxp8u61q on Monday October 09, 2023 @11:20AM
(#37821354)
On my keyboard layout it's one keypress. And since code is read about 100 times as much it's written, I don't particularly care about reaching 250 WPM while writing code. The difficulty of writing code is thinking about it, not actually physically writing it.
Re:My personal C coding style as of late 2023
by circuit10 on Monday October 09, 2023 @11:24AM
(#37821401)
Integer types are very common so it does still get a bit tedious. I guess it causes clutter when reading too
Re:My personal C coding style as of late 2023
by seanw444 on Monday October 09, 2023 @09:06AM
(#37820072)
How about... u32?
Re:My personal C coding style as of late 2023
by slikrick on Monday October 09, 2023 @09:30AM
(#37820287)
gasp blasphemy! C programmers literally can't have nice things
Re:My personal C coding style as of late 2023
by uxp8u61q on Monday October 09, 2023 @11:32AM
(#37821476)
Sure, that's totally readable and meaningful.
Re:My personal C coding style as of late 2023
by oaiey on Tuesday October 10, 2023 @01:49PM
(#37835167)
Unsigned 32 bit IEEE 754 floating point, right?
Re:My personal C coding style as of late 2023
by circuit10 on Monday October 09, 2023 @09:12AM
(#37820125)
It’s longer than it needs to be when you’re typing it out so many times