Re: "A diagram of C23 basic types"

On Fri, 4 Apr 2025 17:12:42 +0200
David Brown <david.brown@hesbynett.no> gabbled:

On 04/04/2025 16:10, Muttley@DastardlyHQ.org wrote:

On Fri, 4 Apr 2025 13:39:06 +0200
David Brown <david.brown@hesbynett.no> wibbled:

On 04/04/2025 11:40, Muttley@DastardlyHQ.org wrote:

On Thu, 3 Apr 2025 15:58:05 +0200
David Brown <david.brown@hesbynett.no> wibbled:

Human readers prefer clear code to comments.  Comments get out of sync -
code does not.

>
Thats not a reason for not using comments.

>
It is a reason for never using a comment when you can express the same
thing in code.
>
If that's your problem, write better code - not more comments.

 Ah, the typical arrogant programmer who thinks their code is so well written
that anyone can understand it and comments arn't required. Glad I don't have
to work on anything you've written.

>
Arrogance would be judging my code without having seen it.  Writing code that is clear and does not require comments to say what it does is not arrogance - it is good coding.

Any sufficiently complicated code requires comments. Thats why comments exist.
The fact that you think you're code is so amazing that it doesn't says a lot
about you. And no, it isn't that you're an incredible dev, more the exact
opposite.

Rubbish. A lot of the time what is being done is just as obtuse as why.

>
That can /occasionally/ be the case.  But if it happens a lot of the time, you are writing poor code.  It's time to refactor or rename.

I'm guessing you've never written any sufficiently complicated code where
there may be numerous steps to create a single action.

int main()
{
colour_to_hex(10);
return 0;
}

>
UB.  It's /your/ fault.

Yup, you are one of *those* devs.
Rest of self justifying blah snipped.

Just assuming they'll always pass parameters within limits is not just
cretinous, its dangerous.

>
Nope.  It is how software development works.  If you don't understand

It really isn't. Get out of your bunker some time.
tl;dr