So what? We do not actually get to know about the computer architecture while programming in C, right?

Maybe not such fundamental things. But memory heap, allocation stuff, and so on. Not alu of course

This is not UB, it is VALID C

So, this is not computer architecture stuff, but OS But we learn how to use it, but not how it works You can learn to allocate memory in the C# the same way

So what?

How does it prove that the language is WELL designed if it allows to do such stupid stuff?

How does it prove that the language is WELL designed if it allows to do such stupid stuff?

But what about microcontrollers? You can write directly to registers on AVR for example. Registers are a part of architecture

No, I do not think so char* foo = "Hello"; Is this the example of the good design?

Registers are not part of the C language :)

But it is only one example, and I am sure it’s somehow written in standard

Yes, but part of architecture :) avr library gives you interfaces and macros to work with it

Yeah, in the standard it is written that it is legal > But it is only one example Yet you never provided any example what is good about C Maybe implicit conversion? :)

Ok, I can provide such example. The variable declaration is mirror of how you use it

I do not understand you Do you mean that C invented variable declarations?

No, it’s not. But even if it’s not. There are a lot of stuff in C from Fortran for example. It doesn’t make it bad

I do not understand "mirror of how you use it"

I do not understand "mirror of how you use it"

Can you please elaborate your thought?

Can you not do stupid stuff in C++?

Sure. It’s clear how to use variable when you see it’s declaration

When you declare an array of pointers for example int *p[2]; In declaration you can see the same sequence of operators like if you will use it: *p[0]

When you declare an array of pointers for example int *p[2]; In declaration you can see the same sequence of operators like if you will use it: *p[0]

You should initialize it before dereferencing the array pointer.

It doesn't help after you pass your lessons on pointers and arrays void (*foo[])(void (*)(int), int(*)[42]); But now, if you're praising variable declaration style in C, can you without a bottle of vodka say what's the type of foo?

If you take an element on index [0] you’ll get a pointer. You get the int by dereferencing it. Declaration tells you how to reach that int

I can say, but it’ll be too long to write it there :)

It doesn't help after you pass your lessons on pointers and arrays void (*foo[])(void (*)(int), int(*)[42]); But now, if you're praising variable declaration style in C, can you without a bottle of vodka say what's the type of foo?

So you think that it is a good variable declaration style?

The good declaration style is use of typedefs

It doesn't help after you pass your lessons on pointers and arrays void (*foo[])(void (*)(int), int(*)[42]); But now, if you're praising variable declaration style in C, can you without a bottle of vodka say what's the type of foo?

It’s simple to read this: typedef void (*func1)(int); typedef int (*arr1)[42]; typedef void (*func2)(func1, arr1); extern func2 f[];

It’s simple to read this: typedef void (*func1)(int); typedef int (*arr1)[42]; typedef void (*func2)(func1, arr1); extern func2 f[];

using func1 = void (*)(int); using arr1 = int (*)[42]; using func2 = void (*)(func1, arr1); That's easier, don't you think?

using func1 = void (*)(int); using arr1 = int (*)[42]; using func2 = void (*)(func1, arr1); That's easier, don't you think?

It’s kinda the same, except the names come in the beginning. For me typedef version is comfortable

You're just old school

Maybe) But not old school enough to use K&R. I prefer C11

I prefer C++20 :)

I prefer C++20 :)

using func1 = void (*)(int); using arr1 = int (*)[42]; using func2 = void (*)(func1, arr1); That's easier, don't you think?

But, at the end, you still can cast it to void* and nothing will change. But it’ll be harder to get some element from it

And I hate C

If you take an element on index [0] you’ll get a pointer. You get the int by dereferencing it. Declaration tells you how to reach that int

That's right, but, just to be sure, did you mean using it like the way you wrote? int* a[2]; *a[0]; // eg, *a[0] = 5; or like that?

c++ is c with classes lol

Yea, *arr[]

c++ is c with classes lol

You should initialize a pointer before dereferencing it.

It was c with classes when Bjarne introduced it. But it’s no longer c with classes. It’s two completely different languages, but syntax looks kinda the same

Yeah I know just Joking

I mean if you already initialized it you can use it this way

Best way it to code, don't fall into tutorial hell. I started last year

What if i don't know anything about coding then how can I code -_- ?

i only know a little coding

Because you are a beginner. Most people start coding not knowing what they are actually doing; programming and coding are not the same. You must have a sound understanding of the field in general before you dive deep; also C++ is not a recommended language for beginners as it has too many features and you can easily get overwhelmed.

Hi all, I have a problem using a handler for a SIGINT, when I click ctrl+d it prints the message put in a printf many times, even though there is no loop, has anyone ever had the same problem?

True 👍 He will left coding after he get into pointers concept or oops He must start with python or Java i think And he even have not done c🥲🥲

There're some facilities in modern C++ that make it easier persistently. concept (and requires to get rid of SFINAE and its stuff), fold expressions, auto , and many more tools are great helpers. There's also a considerable number of different containers that assist you much in different situations. There're references, raw and smart pointers in C++. (While there's only raw pointers in C I guess) So using modern C++, say, C++23, you will have less worries.

But both languages are not great

C definitely has its place for really low level software like kernels vms or jits

GraalVM and V8 don't agree with you

guys, i dicided to start c language . is it good for a beggining

GraalVM and V8 don't agree with you

True but LuaJIT does And it’s faster than both I think a reduced C++ feature set is the best way to go. C++ makes it hard to see what’s going on behind operations sometimes. I prefer C for really low level stuff, there are less pit falls. For high performance applications or other stuff C++ is amazing.