Because telegram interprets it as a bold text or smth

#include<stdio.h> int main() { int age; char ms,sex; printf("enter age ,ms,sex:\n"); scanf("%d %c %c",&age,&ms,&sex); (ms=='M'?printf("ENSURED"):(ms=='U'&&sex=='M'&&age>30||sex='F'&&age>25?printf("ensured"):printf("unendured"))); return 0; }

No it's like T9

Whem I copy to the grup, in my cod it is look like int 2star а (int 2star ) star is *

#include<stdio.h> int main() { int age; char ms,sex; printf("enter age ,ms,sex:\n"); scanf("%d %c %c",&age,&ms,&sex); (ms=='M'?printf("ENSURED"):(ms=='U'&&sex=='M'&&age>30||sex='F'&&age>25?printf("ensured"):printf("unendured"))); return 0; }

\*test \*

Whem I copy to the grup, in my cod it is look like int 2star а (int 2star ) star is *

even **test is ok, you need a pair of them

this is not markdown

Ah, sorry

# Heading 1

int arr = (int)malloc(r * sizeof(int*)); for (i = 0; i < r; i++) arr[i] = (int*)malloc(c * sizeof(int*)) I will create an array in this way, ie with pointers and the array itself, the array itself can be released, if I'm not mistaken with the function free (array name), but how to be with pointers, I do not understand. Is it enough to write something like free (array name [i])?

Only for bold italic underscore monospace and strikethrough i think

int arr = (int)malloc(r * sizeof(int*)); for (i = 0; i < r; i++) arr[i] = (int*)malloc(c * sizeof(int*)) I will create an array in this way, ie with pointers and the array itself, the array itself can be released, if I'm not mistaken with the function free (array name), but how to be with pointers, I do not understand. Is it enough to write something like free (array name [i])?

Uhmm, you forgot NULL handler if malloc failed

You will have to free the individual elements of the array first and then you have to free the array itself.

The array itself I understand how to release, but the elements are not very much

in the reverse order int** arr = malloc(N * sizeof(*arr)); for(int i = 0; i < N; ++i) arr[i] = malloc(M * sizeof(*arr[i])); for(int i = 0; i < N; ++i) free(arr[i]); free(arr);

The array itself I understand how to release, but the elements are not very much

vector <int> :: iterator IT; Why we use :: Why don't '.'

vector <int> :: iterator IT; Why we use :: Why don't '.'

For each array element you have to do a free(array[ i ]). And for the array, free(array)

Thank you very much that is what I not understand. Thank you

In general there's a rule that destruction must be in the reverse order of construction. Construction goes from top to bottom. And destruction from bottom to top(smallest objects destroyed first)

Actually your example code also should do it. Your for loop should be for (i = N-1; i >= 0; --i) But this is not a problem. Usually it can be a problem if objects share state which is why the standard library containers do it that way.

If I recall correctly delete[] does do that from N-1 to 0, doesn't it?

If I recall correctly delete[] does do that from N-1 to 0, doesn't it?

If I recall correctly delete[] does do that from N-1 to 0, doesn't it?

If the value of the operand of the delete-expression is not a null pointer value, the delete-expression will invoke the destructor (if any) for the object or the elements of the array being deleted. In the case of an array, the elements will be destroyed in order of decreasing address (that is, in reverse order of the completion of their constructor; see 12.6.2).

I am talking about the individual frees (i.e freeing of the elements in the array) in your example code. free(arr[ i ]) should be in the reverse order. If you allocate arr[1] before arr[2], you should ideally free arr[2] before arr[1].

Ideally yes. But free doesn't have a side-effects like a destructor does. So your pc probably won't catch fire if you free in ascending order

Hello friends, I hope you are all well. I'm going to ask you a question that I know is typical of people without programming knowledge, but let me explain the context. I already know programming in PHP and JavaScript, also in C and C++ although I am a beginner in these two. Now, at the university I must focus on one of the two, and I ask you this question so that it can be answered from a personal point of view, which one would you focus on? , C or C++ and why? Sorry if my english it's not perfect.

Hello friends, I hope you are all well. I'm going to ask you a question that I know is typical of people without programming knowledge, but let me explain the context. I already know programming in PHP and JavaScript, also in C and C++ although I am a beginner in these two. Now, at the university I must focus on one of the two, and I ask you this question so that it can be answered from a personal point of view, which one would you focus on? , C or C++ and why? Sorry if my english it's not perfect.

Your English is ok

c++ is harder

I do not have doubt of this. But it has several advantages. And you can even do things that can also be done in C. Not all of course.

> Not all of course. This is not true

I do not have doubt of this. But it has several advantages. And you can even do things that can also be done in C. Not all of course.

Does the clion support modules?

CLion is an IDE. The question of support for modules is dependent on the underlying compiler. As of now only VS 2022 supports all PRs on Modules. G++ supports a majority of it and Clang is yet to implement 4 PRs. If you are going to use your own modules, you are good to go with any of these compilers. If you are going to be dependent on std modules, then your only choice is Visual Studio.

Or by static analyzer built-in to Clion

Maybe he asks about support in cmake

All build systems like build2, cmake and ninja have already added support for modules AFAIK. CMake am not sure that it supports all of it. Even otherwise all the build managers do require support from the underlying compiler

Anyways, I think modules as a language feature won't be production ready for a long time

Yeah i wasn't sure about cmake. I use build2 and it has awesome support. Looks like cmake is still in experimental stage but the reviews seem to be ok so far. Ninja supports modules on an experimental basis as well but it has been out for a while now. Modules are supported well by all major compilers as far as you are using modules that you define without templates code. The problematic issues are P1103R3 and P1815R2. The idea of prohibiting exposure of internal linkage constructs in template code is currently very difficult to implement in Clang and GCC because of the way they handle the augmented AST after the semantic analysis phase. This change requires considerable changes to how Clang and GCC handle the ASTs. This was a problem that was discovered later and so the compiler implementers could not voice their disagreement over this. This is where both GCC and Clang are stuck and it will be a considerable while before support for this is added. But this should not prevent people from mixing header files and modules in their code till this is resolved. Moreover most of the companies are still using only a C++17 (14) compiler. So the slow support for C++20 should not be an issue. This would be surely addressed before C++23 is ratified. Even otherwise, it would be another 1 or 2 years before organizations world wide would start moving to a C++20 toolset.

No, it's not really necessary now C++17 is quite enough And for our codebase there are not many features that would increase developer's experience

No, it's not really necessary now C++17 is quite enough And for our codebase there are not many features that would increase developer's experience