const char const * const post = "Why are C type declarations so stupid?";

>>105730121 (OP)
> rust tranny flamewar thread #4983459839845
nobody cares, permanently unemployed rust tranny. kill yourself, thanks.

In Rust it's just
let post = "Why are C type declarations so stupid?";

I stopped caring since I don't have to use it beyond porting from it.

>>105730121 (OP)
literally no one writes code like this retard

Meanwhile -std=gnu23 chads:
auto post = "works on my machine";

>>105730121 (OP)
D doesn't have this problem

>>105730121 (OP)
who taught you to do that? was it Dr Mr Durga?
go demand a refund of your tuition and ritual seppuku from whoever did that to you.

>>105730121 (OP)
>Why are C type declarations so stupid?
Perhaps it's not the declarations which are stupid.

>>105731067
thats because nobody uses it

Can a C greybeard explain what each const means here?
I love C but I'd just do a const w_char* post = "Why are C type declarations so comfy?";

>>105733450
>Can a C greybeard explain what each const means here?
what op posted is not valid c, there is at most 2 consts in a variable decl, so it should be:
const char* const post =


and its actually not that complicated. The first const char is the pointed to type, a const char. The second const after the * is for the pointer itself, it means the pointers value (what it points to) cannot be changed either.
So you cant do:
const char* const post = "1";
post = "2"; //cant reassign the pointer because its const

>>105733569
>what op posted is not valid c
duplicate const is valid

>>105733569
Ah, ic makes sense.

>>105733607
true but still completely redundant to put it there

const was a mistake

>>105730121 (OP)
>>105730396
>>105731142
>no one should write code like that anyways
Meanwhile when someone posts some javascript nonsense like
null == 0; // false
null >= 0; // true

you shit and piss yourselves over it

>>105734299
C standard specifies that NULL should be interpret as == 0.

an imutable pointer to an ummutable object on my heckin computer!??!? NO THANK YOU.

>>105734315
That has absolutely nothing to do with javascript. Not sure why you feel entitled to have an entirely separate language conform to your specification

>>105730121 (OP)
(((unsigned char)(unsigned *char))const char const * post)

myth: busted

>the fucking retard think that >>105734299 is acceptable behavior
absolute fucking retard

>>105730121 (OP)
no one uses that type

>>105730254
you can use auto in C/C++ as well
what is your point

>>105734299
because this is objectively retarded

>>105730121 (OP)
everything to the left of * is one type. so what is the type const char const?
it's exactly the same as const char. OP just added in another const to shill rust and bait people into testing if it actually compiles.

>>105730121 (OP)
This probably fucked up his c2rust translator.
You know… the thing that generates 99.99% of all rust code in existence.

void (*signal(int, void (*fp)(int)))(int);

So readable.

>>105730121 (OP)
remove the first const and it's perfectly clear
char const * const post = "";

modifiers on the right always affect the left, so the underlying char is const and the pointer is const
allowing modifiers to also be on the left was a mistake, there should only be one direction

>>105736876
typedef void (*signal_handler)(int);
signal_handler signal( int sig, signal_handler f);

it really is that simple.

>all these posts talking about Rust out of nowhere
Rent free lmao

>>105730121 (OP)
Because C itself is stupid. C is the enshittification of programming.