Why can't users provide links to their training courses??? even if it’s an advertisement like “my course is the best.” in any case, the person tried and made these courses for those who want to learn C/C++

Why can't users provide links to their training courses??? even if it’s an advertisement like “my course is the best.” in any case, the person tried and made these courses for those who want to learn C/C++

I'll probably get a ban for advertising the creator's book? Truth Madhu ?

Tutorial for Russian / Ukraine: ravesli com I started with this. Very good course

Creator's book? You mean Bjarne Stroustrup's books or K&R C

I meant the creator

Tutorial for Russian / Ukraine: ravesli com I started with this. Very good course

I just took a cursory look (not more than 2 minutes) at that site with English translation. It seems ok but I will let others like @unterumarmung confirm

I just took a cursory look (not more than 2 minutes) at that site with English translation. It seems ok but I will let others like @unterumarmung confirm

It's transled learncpp AFAIK

It's transled learncpp AFAIK

Tutorial for Russian / Ukraine: ravesli com I started with this. Very good course

https://t.me/cpp20programming/184 Really good courses for Russian speaking learners are listed here at the end

Are you sure that beginners are ready to watch videos for 1 hour+

If one is not ready, why even bother learning?

#cpp So, I have this code, main.cpp #include <iostream> #include <cstdint> #include <cassert> int main() { char *val = (char *)malloc(5); if (val == nullptr) { std::cout << "not ok\n"; return 1; } assert(val); return 0; } The assert() here is like a macro function which does static_cast to bool and does ternary condition or atleast based on what I have observed through linting by VSCode. From assert.h / <cassert>, #define assert(expr) (static_cast <bool> (expr) ? void (0) : __assert_fail (#expr, __ASSERT_FILE, __ASSERT_LINE, __ASSERT_FUNCTION)) The code in main.cpp works as expected and there were no errors. Then, I was working on a legacy codebase, which had the same format as the code observed in main.cpp, particularly, these two lines.. ... char *val = (char *)malloc(5); assert(val); ... Here I got an error. error: invalid ‘static_cast’ from type ‘char*’ to type ‘int' How? assert() does static_cast<bool> though, which worked fine on the main.cpp, but not here. Both code used C++11 standard and gcc-11.

#cpp So, I have this code, main.cpp #include <iostream> #include <cstdint> #include <cassert> int main() { char *val = (char *)malloc(5); if (val == nullptr) { std::cout << "not ok\n"; return 1; } assert(val); return 0; } The assert() here is like a macro function which does static_cast to bool and does ternary condition or atleast based on what I have observed through linting by VSCode. From assert.h / <cassert>, #define assert(expr) (static_cast <bool> (expr) ? void (0) : __assert_fail (#expr, __ASSERT_FILE, __ASSERT_LINE, __ASSERT_FUNCTION)) The code in main.cpp works as expected and there were no errors. Then, I was working on a legacy codebase, which had the same format as the code observed in main.cpp, particularly, these two lines.. ... char *val = (char *)malloc(5); assert(val); ... Here I got an error. error: invalid ‘static_cast’ from type ‘char*’ to type ‘int' How? assert() does static_cast<bool> though, which worked fine on the main.cpp, but not here. Both code used C++11 standard and gcc-11.

#cpp So, I have this code, main.cpp #include <iostream> #include <cstdint> #include <cassert> int main() { char *val = (char *)malloc(5); if (val == nullptr) { std::cout << "not ok\n"; return 1; } assert(val); return 0; } The assert() here is like a macro function which does static_cast to bool and does ternary condition or atleast based on what I have observed through linting by VSCode. From assert.h / <cassert>, #define assert(expr) (static_cast <bool> (expr) ? void (0) : __assert_fail (#expr, __ASSERT_FILE, __ASSERT_LINE, __ASSERT_FUNCTION)) The code in main.cpp works as expected and there were no errors. Then, I was working on a legacy codebase, which had the same format as the code observed in main.cpp, particularly, these two lines.. ... char *val = (char *)malloc(5); assert(val); ... Here I got an error. error: invalid ‘static_cast’ from type ‘char*’ to type ‘int' How? assert() does static_cast<bool> though, which worked fine on the main.cpp, but not here. Both code used C++11 standard and gcc-11.

#cpp So, I have this code, main.cpp #include <iostream> #include <cstdint> #include <cassert> int main() { char *val = (char *)malloc(5); if (val == nullptr) { std::cout << "not ok\n"; return 1; } assert(val); return 0; } The assert() here is like a macro function which does static_cast to bool and does ternary condition or atleast based on what I have observed through linting by VSCode. From assert.h / <cassert>, #define assert(expr) (static_cast <bool> (expr) ? void (0) : __assert_fail (#expr, __ASSERT_FILE, __ASSERT_LINE, __ASSERT_FUNCTION)) The code in main.cpp works as expected and there were no errors. Then, I was working on a legacy codebase, which had the same format as the code observed in main.cpp, particularly, these two lines.. ... char *val = (char *)malloc(5); assert(val); ... Here I got an error. error: invalid ‘static_cast’ from type ‘char*’ to type ‘int' How? assert() does static_cast<bool> though, which worked fine on the main.cpp, but not here. Both code used C++11 standard and gcc-11.

I can't say why, but I think you shouldn't pay attention to it and just use explicit typing yourself. I wrote above that it is recommended to use exactly such types that are used in the function

The problem is that, even when I explicitly use something like, char *val = (char *)malloc(5); bool someVal = static_cast<bool>(val); I get, error: invalid ‘static_cast’ from type ‘char*’ to type ‘int' 💀 Since it's legacy codebase and it imports a lot of headers, is there a chance or possibility that somewhere in those user defined headers, there would be a custom assert macro/function ? Are user-defined functions have more precedence over a standard library one ?

You're having a little trouble with the pointers. I'll explain it to you in a moment, I can send you a message.

I'm ashamed to admit, but yes, I am having trouble with pointers for years.

Probably the assert in the legacy codebase defined differently

I'm ashamed to admit, but yes, I am having trouble with pointers for years.

I'll send you private messages?

Explain here.

you must have already read that pointers = address in memory Let's go straight to the examples to make things clearer: int a = 10; int *b = &a; // get the address of a b is a pointer to MEMORY. it does not store the value 10. Now let's move to the memory pointed to by b. To do this, we need to DIFFER it (add *). int c = *b; // now c stores value 10

By DIFFER you meant dereference, right?

By DIFFER you meant dereference, right?

I guess i can try, what seems to be your issue? I am too lazy to scroll back up :D

I guess i can try, what seems to be your issue? I am too lazy to scroll back up :D

#cpp So, I have this code, main.cpp #include <iostream> #include <cstdint> #include <cassert> int main() { char *val = (char *)malloc(5); if (val == nullptr) { std::cout << "not ok\n"; return 1; } assert(val); return 0; } The assert() here is like a macro function which does static_cast to bool and does ternary condition or atleast based on what I have observed through linting by VSCode. From assert.h / <cassert>, #define assert(expr) (static_cast <bool> (expr) ? void (0) : __assert_fail (#expr, __ASSERT_FILE, __ASSERT_LINE, __ASSERT_FUNCTION)) The code in main.cpp works as expected and there were no errors. Then, I was working on a legacy codebase, which had the same format as the code observed in main.cpp, particularly, these two lines.. ... char *val = (char *)malloc(5); assert(val); ... Here I got an error. error: invalid ‘static_cast’ from type ‘char*’ to type ‘int' How? assert() does static_cast<bool> though, which worked fine on the main.cpp, but not here. Both code used C++11 standard and gcc-11.

alright i see the problem. Lemme ask you a few questions int* p = 3; What does this mean?

A pointer to an address where 3 is stored ?

Not entirely correct. Lemme ask you one more question before i explain everything int a = 3; What does this do? Gimme the most detailed answer, if possible.

a is a name we give to an object. Here thr object is an integer stored at some place in memory. Since we have given a name for that object, it is a variable ?

What type is a pointer then, I assume something like, unsigned int/long to store large numbers (address) ?

int* p = &a; Now what you do is you tell it that i want this pointer to store the address of a, that is i want p to point to a.

I think I get it now..

int* p = 3; int a = 32; // assume it's stored at memory location 0xb10 (binary repr) So what will std::cout << *p; print?

Some garbage value ?

No it'll print 32

Wait isn't 0xb10 2 in decimal ?

If it was 0xb11 then it would be 32

Well you get it then

#cpp So, I have this code, main.cpp #include <iostream> #include <cstdint> #include <cassert> int main() { char *val = (char *)malloc(5); if (val == nullptr) { std::cout << "not ok\n"; return 1; } assert(val); return 0; } The assert() here is like a macro function which does static_cast to bool and does ternary condition or atleast based on what I have observed through linting by VSCode. From assert.h / <cassert>, #define assert(expr) (static_cast <bool> (expr) ? void (0) : __assert_fail (#expr, __ASSERT_FILE, __ASSERT_LINE, __ASSERT_FUNCTION)) The code in main.cpp works as expected and there were no errors. Then, I was working on a legacy codebase, which had the same format as the code observed in main.cpp, particularly, these two lines.. ... char *val = (char *)malloc(5); assert(val); ... Here I got an error. error: invalid ‘static_cast’ from type ‘char*’ to type ‘int' How? assert() does static_cast<bool> though, which worked fine on the main.cpp, but not here. Both code used C++11 standard and gcc-11.

Dm me

If you can answer this question that'll be nice. I didn't go that much into types but you should be able to.

But, suppose that was not a mistake, but intentional, then the value printed can be whatever the data that was in that specific address at that point right?

You mean like finding the mistake?