Re: "A diagram of C23 basic types"

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.

>
Comments should say /why/ you are doing something, not /what/ you are doing.

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

Except its not unreachable is it?

>
It /is/ unreachable.  That's why I wrote it.

Really?

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

You have no idea how someone might try and use that function in the future.
Just assuming they'll always pass parameters within limits is not just
cretinous, its dangerous.

 There's nothing in C to prevent you
calling that function with a value other than defined in the enum so what
happens if there's a bug and it hits unreachable?

>
There's nothing in the English language preventing me from calling you a
"very stable genius" - but I can assure you that it is not going to happen.

Poor analogy.

Oh thats right , its
"undefined" ie , a crash or hidden bug with bugger all info.

>
Welcome to the world of software development.  If I specify a function
as working for input values "red", "green", and "blue", and you choose
to misuse it, that is /your/ fault, not mine.  I write the code to work
with valid inputs and give no promises about what will happen with any
other input.

Its your fault if it dies in a heap with no info or worse returns but does
some random shit. Any well written API function should do at least basic
sanity checking on its inputs and return a fail or assert unless its very low
level and speed is the priority eg strlen().

But then you're arrogant, so no surprise really.

Also FWIW, putting seperators in the hex values makes it less readable to me
not more.
 

>
Again, that's /your/ problem.

See above.