News for hackers. Stuff that matters.
Re:My personal C coding style as of late 2023 by seanw444 on Monday October 09, 2023 @09:13AM (#37820132)
When we move into the 128-bit CPU era, will we call 128-bit integers "super long"? Maybe "elongated". Maybe "huge"?

Or, you know, we could just name them all by bit length and completely future-proof this system.

Re:My personal C coding style as of late 2023 by richard_todd on Monday October 09, 2023 @10:07AM (#37820594)
We used to call 16-bytes a paragraph, so the nostalgic geek in me would love to see ‘para’ catch on. I never thought I’d be slinging around whole paragraphs of memory in registers!
Re:My personal C coding style as of late 2023 by ogogmad on Monday October 09, 2023 @11:11AM (#37821270)
Why would we ever need 128-bit CPUs? I remember the PS2 had something like that (with details and caveats I don't understand), but subsequent games consoles went back to a more usual register size: https://en.wikipedia.org/wiki/128-bit_computing
Re:My personal C coding style as of late 2023 by seanw444 on Monday October 09, 2023 @11:49AM (#37821659)
All I know is we keep having this issue with saying "nah, this is it. Nobody will ever need more than this." And then inevitably the time comes when we need more.
Re:My personal C coding style as of late 2023 by WalterBright on Tuesday October 10, 2023 @01:09AM (#37828704)
Back in the 80s, 16 bit programmers knew that 32 bit code was coming, so they carefully crafted the code to be portable to 32 bits.

Of course, none of it worked on 32 bit machines because the programmers had never written 32 bit code before and did the portability measures all wrong.

Re:My personal C coding style as of late 2023 by WalterBright on Monday October 09, 2023 @02:20PM (#37823445)
We call them "cent" and "ucent" in D :-)