Yes, you're right. I should have defined it as *char name[] = "Cherno";* in that example.

Please what is the difference between: char* a = "Cherno"; a[2] = 'a'; output is:error and char* a = "Cherno"; a = "Charno"; std::cout

Yeah, I saw that the address is changing sorry

Стефан Рибак In the second alternative, you aren't changing the memory the pointer "a" points to. You are changing the value of the pointer "a" to point to other place that contains other char string (with the same letters). I think this could seems difficult, so I'll try to explain better: char *a = "Cherno"; creates a pointer "a" that points to a memory that contains the letters "Cherno". a = "Cherno"; change the value of the pointer "a" to point to other memory that also contains the letters "Cherno". So, later you can also do a = "A big string like this"; and it will work too, because "a" will point now to a new memory. The old memories with "Cherno" will remain unchanged somewhere in memory.

Mario Galindo oh thank you for explaination) it helps me a lot in the future)

That's what I'm doing. A lot more useful content here than in Netflix

​@haru02w89 it's not useful if you don't actually go and code a lot

bing bing. bing ing.

C++ is addicting af when I watch this guy

Do you sell his videos? :D (joke)

damn right!

Agreed!

It definitely is. Yan is the kind of programmer I'm aspiring to become. He's such knowledgeable and proficient (he's also pretty handsome 😳)

I would you said "eres un bebe precioso" (You are a precious baby Cherno) hahaha

I had heard similar from many folks, but as I recently started to look into learning a systems capable language comparing various advantages of each(both direct features and meta stuff like maturity, guide books, and employment) I found I kept coming back to C++. C++ was ISO standardized in 1998, then a major update in 2011, with minor additions in 14 a few in 17 and several predicted for 2020. I also discovered that "C/C++" is an incorrect term as the ISO C standard is not synchronized with the C++ standard; C++ is an independent fork from before C89. Many negative C++ opinions seem to be based on experience [or for younger folk repetition of urban legends] from the early 1990s. (partly exaggerated by articles and postings created by Sun's heavy Java marketing efforts and stubborn old timer C devs) Certainly not helped by education curricula that frequently uses 20 year old books and compilers, and a teacher that has been out of the commercial game for so long their "best practices" have been deprecated.

it doesn't work if my code is like - { char* name = "cherno"; std::cout

@@takitachibana7717 See the pinned comment

@@MrCoder-xj9yii already know.Thanks anyway man.

​@@takitachibana7717 It works for me, but I'm on Linux with gcc compiler. But if I try to change it I get segmentation fault, becase the memory referenced is read only memory protected from writting to it.

I addressed most of these in my video on string literals. :)

Advitiay Anand your*

so excited for our own data structures!!

kk bro

(Warnings don't break your code. In fact, they have absolutely no effect in your program. It's only a little message that says something is a little off with your code, but it will still run)

EXACTLY I WAS THINKING THE SAME XD

the way the char* and char[] strings work in C/C++ is so: the text inside the double quotes is broken up into individual characters, and those characters are stored in a char array, with a '\0' as the last element of the array. The pointer itself points to the adress of the first element of the array, the beggining of the string, while the end of it is marked with the '\0' char.

the type of a quoted string literal, such as "Cherno", is actually char*. That is, a quoted string literal IS actually an address. An address of what? It is the address of the first character in the string. That means that the entire construct "Cherno" - including the double quotes - actually equals to the address of the first character, 'C' in this case. The reason for this is that the compiler stores the string literal ("Cherno") in memory, and it only remembers the address of the strings' beginning character ('C' in our case.) All the program needs to actually use this string is use the address of its first character. The terminating null character '\0' takes care of marking the end of the string literal.

@@vitorkiguchi4670 I know this is an old comment, however you say the following: 'The pointer itself points to the address of the first element of the array.' Shouldn't it be the case that this pointer IS the memory address for that first element? And if so, why then does cout

@@ArachnosMusic operator

@@vitorkiguchi4670 I read your answer and i think you can help me to solve this error. So, I got an error when I run the code below . //// char* name="learn"; std::cout

while using a breakpoint: in the ‘debug window pane’ right mouse click on the variable of interest -> in the drop down menu that opens, left mouse click on ‘ view memory of “...variable...” ‘ ( as is demonstrated in ‘visual studio’ ) does anyone know how to get a ‘tool tip’ to display of the address of a variable while the mouse cursor is over the variable ??? & is there a way to enter the variable name into a text box that then displays the variable’s values in the memory window pane ? [as an alternative to the solution provided above]

its just making an empty string with nothing in it but also making sure it isn't null so if something tried to get that destination it wouldn't just crash the program when it doesn't get a string out of it.

well it would just put the '\0' at the memory location

to be more precise the const char pointer would point at a char of value 0

Yes, you're right. I should have defined it as *char name[] = "Cherno";* in that example.

Append is just a heap thing

A traditional terminal screen or printer interprets all bytes as part of a character set. Actual numeric values such as integers must be converted to the corresponding characters before being sent to the screen. Thus the need for cout or printf formatting functions.

hey says this in a previous video :)

What's wrong with having both discord and slack - they are actually different tools.

If you ask me, nothing. I just personally don't like to use many tools for the same reason. :) Also as far as I know both are live now, so if you like to use both, you can have the benefit of joining both conversations.

Don't use C-style casts in C++ programming. C-style casts are the most dangerous ones.

From what I have heard, 'using namespace std' is often considered bad practice. Apparently there is so many classes and functions in that namespace that it is not unlikely that you will accidentally name a function or class the same as something in the std namespace. I have heard from several developers that they have spent a lot of time debugging code that used 'using namespace std' due to name conflicts

the c++ string class does give you functionality to get the length of the string. If you use a char* or a char[] you need to keep track of the length yourself, and that would speed up any slowdown that could occur by needing to loop over the whole string to get the length. I hope this helps :)

yes, but the function to look up the length is a while loop until you reach the null character, isn´t it?

oh it might be. I didn't think about that. I'm sorry. I don't know the std library that well. I usually make my own data structures unless I'm making something quick ad dirty. so I never took the time to learn exactly what happens under the hood. but if that is the case I would suggest to make your own string class that would suit your needs and keep track of the length automatically so it speeds up that operation. :)

It is for raw char pointers or char[], however std::string has a member (an int) which keeps track of the size, so no counting necessary.

Bad memory allocation you have

LOL

Room acoustics. Also explains why his voice sounds relatively shallow in the mid-range and slightly boosted on the low end. He could fix a fair amount of that just by turning at a slight angle to the wall or putting up something textured on the wall in front of him.

Yes, no need to add header in 2022

What's faster? Copying a pointer, or allocating memory and copying data?

James Nguyen depends on the size of the data

std::cout works differently with different operands You can think of it, basically, as function overloading: you can have functions with identical names but with different input types. Compiler decides what version of the function should be called based on types of the arguments you pass in Pretty much same here, (although I'm not sure that is exactly how standard library is implemented): There is a version of this 'cout function' (technicaly, it's ostream& operator

Will you can type cast if wanted it to print a integer

Probably, that's how std::cout works with strings.

That is exactly what I wanna know too

@@DainYanuka std::cout assumes your intention. If you pass in a const char* data type in the argument, it will interpret your intention as wanting to print out a C-Style string instead of a memory address.

@Artem Katerynych Std ::string are allocated in the heap

They're equal, since they're both evaluated to 0 at compile time.

Thank you!

are you planning to do litle bit of os staff to example how memory is allocated or how compilers work at a deeper level? because we intermediate users also enjoy your videos, you are explaining the material more understandable way also mentioning things that most teachers do nots spend time on.

Yes it is the same Since the array is just a pointer

It is because the next byte was a null

Same for me, how weird.