How Strings Work in C++ (and how to use them)

Patreon ► / thecherno
Instagram ► / thecherno
Twitter ► / thecherno
Slack ► slack.thechern...
In this video we're going to talk about how strings work in C++. Strings are groups of characters between double quotes: "this is an example of a string". We use them to store everything from people's names to entire paragraphs of text, and we can use them like any other variable. Strings are really just char arrays at the end of the day, and this video takes a deeper look at how they work.
std::string API reference ► www.cplusplus.c...
Pointers ► • POINTERS in C++
Arrays ► • Arrays in C++
Series Playlist ► • C++
Gear I use:
-----------------
BEST laptop for programming! ► geni.us/pakTES
My FAVOURITE keyboard for programming! ► geni.us/zNhB
FAVOURITE monitors for programming! ► geni.us/Ig6KBq
MAIN Camera ► geni.us/t6xyDRO
MAIN Lens ► geni.us/xGoDWT
Second Camera ► geni.us/CYUQ
Microphone ► geni.us/wqO6g7K

[@Brotcrunsher]

You've made a mistake at 7:03 "[...] otherwise you can just leave it as a char pointer that is totally fine.", implying that it is okay to change a char in that array. No it is not! That is undefined behavior and leaving a pointer to a String literal non const it deprecated since C++11. You must not change any value of the C-String-Literal!

[@TheCherno]

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

[@forest_grow]

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

[@forest_grow]

Yeah, I saw that the address is changing sorry

[@mariogalindoq]

Стефан Рибак 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.

[@forest_grow]

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

[@Steven-tw7iz]

This is hands down the best c++ series on youtube. Very professional and informational, amazing job once again Yan! Your videos are fantastic!

[@nighma]

Do you sell his videos? :D (joke)

[@ruf1o2o]

damn right!

[@rcookie5128]

Agreed!

[@jorgejarai]

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 😳)

[@bringiton2100]

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

[@danilivanov6262]

Replacing my Netflix binging with TheCherno binging. Loving these videos!

[@BobrLovr]

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

[@whoeverofhowevermany]

bing bing. bing ing.

[@zanagi]

C++ is addicting af when I watch this guy

[@TalisBarbalho]

Even when you say that you were just "mumbling", you still share so much knowledge with us. Thank you for that. Just keep releasing the videos that are easier for you to produce and leave the others for when you have time. Looking forward for the really deep engine programming. Many thanks for the video

[@Gilpow]

10:13 Note that in the console output, there are 25 garbage characters after "Cherno". Exactly the number of bytes in memory, after that strings, before a "00" byte is reached ^^

[@equinox-h9v]

I was actually wondering why there's a set amount of characters printing after Cherno and why the whole console isn't getting filled up with gibberish. This actually cleared that up, thanks.

[@danielketcheson1965]

Your explanation on how you learn best; being taught what works vs how it works makes my inquisitive mind tingle with joy. Even makes me trust your content all the more. I feel this style is empowering to the individual who is seeking to utilize and transfer knowledge to any persons interested.

[@jmac217x]

Every time I think I know a little about something I find out how little I know! Thanks Cherno 5 years later your knowledge is still invaluable. The Discord is a great resource

[@leixun]

*My takeaways:* 1. C style string 5:30, and why he uses char* 9:00, because *"anything inside a double quote is a char array"* 14:10 2. C++ style string 11:04 3. Passing a string to function 16:13, it is better to pass by reference to avoid copy

[@takitachibana7717]

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

[@MrCoder-xj9yi]

@@takitachibana7717 See the pinned comment

[@takitachibana7717]

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

[@RandomGuyyy]

I love this style of video where the speaker has a loose conversational style. They naturally wander into tangential subject matter because many things are related. So they feel like they are rambling but I reckon it's just a natural traversal of the subject. Excited to hear mention of a new series!

[@kacperozieblowski3809]

This series is sooo well made, keep making it please

[@CRBarchager]

I haven't played around with c++ since the last 90's (Borland) and use C# these days in my day to day work. This series of c++ gives a great insight how far the language have progressed since then and is a real joy to watch and learn. You clearly know your way around the language and you do it way better than anyone else I've seen through the years on youtube. If you want to make 1, 2, 3 or more videos a week is up to you but I don't mind more with the quality you put out.

[@mytech6779]

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.

[@Krokoklemmee]

neat video, I just want to point out a few things that weren't *entirely* correct: 1.) UTF-16 is not a 16-bit fixed-width encoding. It simply works in *blocks* of 16-bit code units, where a character can be made up of one or two code units. 2.) wchar_t is not guaranteed to be 2 bytes wide, that's only the case on Windows (on most unix-like OS's for example, a wchar_t is 4 bytes long). That's why we got std::u16string :P 3.) Modifying a value previously declared "const" is not "totally fine", it's undefined behavior

[@TheCherno]

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

[@zhaadd]

me casually switching tabs each time his face pops up. i luve the code ohk. keep the great content coming its better than uni omg

[@j4n0w5k1]

Love your stuff, I am a student learning C++, and your channel is my go to when I need help

[@justicefor4ll]

Missed my lecture today on strings, thanks for this! :)

[@obong5241]

The best C++ series on KZbin.

[@IsaacAsante17]

Cherno, I'm your new fan. Your C++ videos are gems.

[@hemangmathur2823]

I love how his eyes match his hoodie.

[@KandMe1]

Well just to say my thoughts are your doing this really well by laying out this ground work for reference once you drop something of a really meaty project. Thanks for this it will help a lot knowing I can go back and go through these at any time. Well done.

[@advitiayanand5974]

I wanna say you're videos have been the most helpful and informative. Seriously man. Keep at it!

[@sypherus.luxiferr5042]

Advitiay Anand your*

[@rcookie5128]

and again expanded my knowledge on such basic concepts like string. I feel enlightened!

[@rcookie5128]

so excited for our own data structures!!

[@ananthteja6357]

kk bro

[@nhanNguyen-wo8fy]

2:27 char 5:25 string of char pointer 8:10 null 14:10 appending 16:14 passing string

[@1st_ProCactus]

These videos are definitely improving my skills. And it will help to understand more of what Bisqwit code(a little). Cheers Dude :)

[@mkdeviphone]

Like your style explaining stuff down to memory level! And you do it so direct! Genius!

[@Usammityduzntafraidofanythin]

The number of asides are BRUTAL in this video

[@DineshGowda24]

I like how u explain c++ and enjoy it. C++ is one the best lovely languages if we understood it properly. Keep up the good work. Just saw ur playlist on c++ gonna watch it all today. Hope u upload more c++ videos.👌👌👌👌👌 Top notch stuff

[@nighma]

Thanks! That's great! Hope to see more next. There are already a bunch of "that will be explained in another video" reference in this serie. I can't wait! Thank you

[@ahumanzr]

I got a nice warning at 5:54 (removing "const") "Conversion from string literal to 'char *' is deprecated [-Wc++11-compat-deprecated-writable-strings]" Essentially, non-const char pointers are deprecated in c++ 11

[@ahumanzr]

(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)

[@nick60444]

Been watching/referencing your videos for years, especially my college days. So thanks Cherno. I had a quick question though, around 17:03, you mentioned that copying a string will have you allocate space on the heap. Did you actually mean the stack? If I remember from C, then everything is pass by value, so you're essentially creating copies of your arguments when calling a function. Space on the stack is allocated for your arguments, so this is where the copy will live.

[@diribad]

The Cherno is a god sent gift lol

[@tarik9563]

I actually very much like the way you write your code. I mean: when you write the idea then make affectations and nominations. thank you.

[@kristinaraciukaityte3451]

I usually dont curse, but this..... this is fcking amazing.

[@sallaklamhayyen9876]

Brilliant explanation thank you so much and please continue we need content about C++ Data Structure STL and more about critical parts in C++

[@sanyi_derda]

4:06 Slight mistake: UTF doesn't work like that. UTF-16 doesn't mean we have 2^16 different characters. UTF is variable length. There are way more possibilities than 2^16.

[@GenericPhantom1]

A string is basically an array of characters, a collection of characters and each of them can be changed.. You type const char* if you don't want to change the value of the string but only char* if you do.

[@Destrio_Fury]

That transparancy is the reason I prefer C++ above Java, of course it's easy to do in Java. But u will forget after some time why u did it, but C++ code will make sure u understand everything before anything works 🤣🤣

[@krec348]

Keep that style of videos, they have are awesome! Magnific

[@OFaruk58]

Amazing video's Just noticed the "Gear I use" All off them are freaking expensive lol

[@Im10105656]

When you do char* name = "Cherno" don't you create a string literal that's read-only? Is name[2] = 'a' is undefined behavior or not?

[@TheCherno]

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

[@alltheway99]

when passing an object as argument, copy is made on stack, 17:18

[@murtazahussain6301]

EXACTLY I WAS THINKING THE SAME XD

[@Trainfan1055Janathan]

What does it mean when there are double quotes with no text in them? For example, in this one script for a tram in a train simulator I play, there's a line of text that reads: string destination = ""; (I'm trying to learn how trains are scripted in this game, so I can make my own scripts.)

[@sacripudding4586]

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.

[@jukit3906]

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

[@jukit3906]

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

[@刘嘉政-d6l]

Hi Cherno, in 13:22 you mentioned that you would get error with "std::cout

[@heavymetalmixer91]

Same for me, how weird.

[@ashishmathewabraham7278]

I really like the fact that you show how the memory view in Visual studio works , which it makes so much clear . I wanted to see this memory view in Xcode . Do you happen to know if the memory view is available in Xcode?

[@anuglybug4473]

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]

[@petarsmilajkov9431]

Great videos man. Needed to brush up on C++ as I haven't used it in years, and I've been 2X-ing your videos all day. Now on 32! Matrix upload-style. What app do you use for screen recording if I may ask? Thanks and keep the videos coming!

[@Idlecodex]

Oh Man.... This is like Game Of Thrones! a Marathon I can only leave if I fall asleep...! Damn it!

[@tigershav]

the more I learn about C++ the more I like it. Coming from Java -> Python -> Js -> C++ I really appreciate being back with a language that is so... "structured"?/strict

[@codewithfelix3940]

this is some fresh breath of c++ here ...

[@rylanjohnson9049]

Might be confusing at first just understand that the reason std::cout prints the string instead of the memory address is just because it interprets it as a C-style string instead of printing the address

[@CacheTaFace]

These videos are so helpful, you are the MAN!

[@1vor12dokus8]

thanks for the vid and all of them, still invaluable years later. One little remark to 13:36 and the overload of the "

[@jiaxiin2769]

Yes, no need to add header in 2022

[@mattjohnson9453]

I think it's also important to note that characters themselves are just numbers; putting single quotes around a character makes it evaluate to a number, the only reason it prints to form text is that single byte numbers are (mostly) interpreted as such. There isn't a whole lot of difference between char txt = 'a'; and int8_t num = 97;

[@mytech6779]

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.

[@falsemotive]

hey says this in a previous video :)

[@SouravChakraborty-y3w]

Thank you so much for this information!

[@tokyoanimeseven]

Bro Your Explanation Is Just Awesome.

[@akielsteewart8577]

13:30 it's nice that it works nowadays without including

[@matteusberg9091]

String is a type of char array. You should pass a string by reference into a function. When declaring a string and you want to use the + operator in order to add two const char arrays togehter, use std::string() on the first char array. declaring a variable as const is simply a promise that could be broken, but shouldn't. Got it!

[@zakesters]

You can output strings with just now, though I think you still need to get all the nifty methods.

[@abderezakabidi4510]

when i write char* name="alex" it return an error that says " a value of type "const char*" cannot used to initialize an entity of type "char*" why

[@sso1328]

The string (in this case, "alex") is a const char*, and you're trying to make it equal to a char* (name), which are not the same. The correct way would be: const char* name = "alex";

[@pattech3960]

@@sso1328 Well the thing is, he was trying to do void main() { char* name = "Alex"; name[2] = 'a'; } like in the video, but it created the error ' a value of type "const char*" cannot used to initialize an entity of type "char*" ' I had the same problem, but I'm just ignoring it now that I am not sure what kind of solution there is to do it. I'll definitely learn it later on for sure.

[@pattech3960]

std::string name = "BAUHAUS"; name[2] = 'S'; std::cout

[@jerfersonmatos28]

Wow, very clear explanation

[@v-for-victory]

Very good explaining and a great series.

[@eliasabdulbaaki6090]

This dude is very good.

[@Lesgunia]

Yeay Discord! That would be so great! I already have other courses that use discord so I did not want to download or join slack. But I would for sure join a discord group. :)

[@gavinw77]

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

[@Lesgunia]

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.

[@xristosbart8217]

What was that about? I mean the thing about the new series. I guess heap allocation, polymorphism and constructor initialization is what's left untill we can get to data stractures, right?

[@majesticmack]

I already know c++. I just watch these vids just to see Yan haha

[@RoshanPradhan2]

Your eyes radiate light!

[@Vego1274]

I really like Your videos :) You should also make a video about C++/CLI and how to use it :) It might be very useful for people who want to use C# from C++. Anyway, good work ^^

[@remak6342]

another EXCELLENT video!

[@Josifer4GAppFire]

I still don't understand how a char* can be a string.. I thought a pointer is just a memory address

[@vitorkiguchi4670]

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.

[@aryesegal1988]

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.

[@ArachnosMusic]

@@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

[@piaIy]

@@ArachnosMusic operator

[@abderezakabidi4510]

@@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

[@cprn.]

Omg, coming back to this video because I didn't use C++ for 6 months and strings are fucking black magic...

[@pball1000]

Good stuff. VERY helpful. Thank you! Im learning so much

[@Murderface666]

Just a random, unrelated fact: From the beginning of this series to this date, I've lost 30lbs from dieting and exercise

[@TheCherno]

Is that because you had to make room for all the C++ knowledge? ;)

[@Murderface666]

yup! Now myself and my code is a lot more lean lol

[@utkarshgupta3]

@@TheCherno ha

[@Quaggabagel]

How you doing know?

[@rbcm1]

Hi Cherno. Where do you stand on using char* instead of string class when coding in C++? Would you always favor the usage of string class or can you think of a reason why not to?

[@xrafter]

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

[@Djzaamir]

great video as always @Cherno

[@gabeastone8793]

This is more to pointers, but how come when you print name you got Cherno? Why isn't the address printed since you didn't deference it?

[@igorthelight]

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

[@DainYanuka]

That is exactly what I wanna know too

[@zoriiginalx7544]

@@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.

[@ArachnosMusic]

Shouldn't it be the case that the pointer 'name' is the memory address for the first element of the const char[] array which is "Cherno"? And if so, why then does cout

[@matt-g-recovers]

I hope that you get to doing data structures and possibly an analysis ot algorithms. I am using your videos to implement the Algorithms outlined in Robert Sedgewick's textbook by the same name. Currently in Java for the 4th edition, the 3rd has C++ implementations, however it was written in 98. so I am trying to redo it with a more modern idiomatic C++. Then smartly use this with Android to prove and measure the performance boost. So far so good man, I am getting the language easily with your help

[@nathancwatkins]

at 13:10, when he says you can change the string (a const char array) by doing "an implicit cast to a char pointer" if we wanted to manipulate the array. Could someone clarify what he means here. I really appreciate it. p.s Love the series! Sorry if im a noob, learing c++ at a cc -

[@BeatSmokerFactory]

Thanks for your awesome content, i watch you since the rain java project and learned so much from your videos, thank you. One question: i heard a joke about c++ strings beeing really slow when appending something to the string, because you do not know the length of the string and have to go through the whole thing in order to get its length and know where to append to. Are there other string classes where the length is stored or is this class still typically used ?

[@Steven-tw7iz]

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 :)

[@BeatSmokerFactory]

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

[@Steven-tw7iz]

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. :)

[@TheCherno]

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.

[@ContentConsumer90]

8:37 name in char* name is a pointer variable and pointer variable is an integer(address value) then how cout

[@ОсипПоддерегин]

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

[@xrafter]

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

[@pavanrameshghate5416]

apart from the study did you pick your channel name from the Pacific Rim movie(cause one of the yager names in that one is cherno Alpha)

[@ppoplawski]

In the example at 15:00 i've also found a way that you can just explicitly cast the " hello!" const char* to std::string (like "Cherno" + (std::string)" hello!";). Is it also a way you would recommend to do concatenation in C++? In other words - are there any disadvantages 'under the hood' while using this method?

[@touchdepp4507]

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

[@mathewmccloskey8242]

Great video, as always :)

[@killakill8731]

why do not use 'using namespace std; ' does it has something to do with performance ? I already researched but I didn't quite understand.

[@alexhorejsi6287]

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

[@brakpseudonimu236]

So what's the difference between char* and other pointers? As I understand, it's just a pointer like any other pointer, and the memory allocation and writing is done by the double quotes function that returns the pointer, right?

[@1234feng]

Thank you ! Can you talk about c++ std::wstring performance slow and how to improve performance ?

[@TheStapleZ]

Please keep making these videos!! :)

[@yasoda1]

Yan, you are a Godsend!

[@93davve93]

Great videos, but you should consider getting a lav mic to boost the audio quality. It is a bit echoey...

[@LucidStew]

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.

[@PsyberSenpai]

Do you have a camera setup video, this video has a distinct look to it

[@daddy9004]

I cant express how valuable those videos are. Thank you so much for doing this!

[@TheSpartan989]

When you were talking about ways to add onto strings, could you use the .append method as another way to add onto the string?

[@xrafter]

Append is just a heap thing

[@tachiibou]

I believe that in the book "Effective c++, 55 specific ways to improve your code" they say that most types from the std library is somehow as effective to copy as it is to just send a reference. Is this wrong? Or maybe I am just remembering wrong.

[@jamesmnguyen]

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

[@pradyumnkejriwal3007]

James Nguyen depends on the size of the data

[@serkanozturk4217]

Personal notes: C style string: Char* name = “john” or const char* string. The reason some prefer const declaration is that once you allocate that memory for string, you cannot extend it and say name = “john wick” -Use std::string for C++

[@b0606089]

Please make a video on wide string

[@stephenjames5745]

Thanks for the awesome videos!

[@monishkumardurairaj3038]

@13:07 if you need to manipulate the contents of const char* try type caseting to char * . i tried converting const char* name="chernno"; *((char*)name+2)='a'; it throws segmentation fault error arises....why?

[@monishkumardurairaj3038]

HI@Peterolen, so there is no way, we could change the contents of a string literal?or is there any. another doubt is strings are immutable... but where this memory is allocated.... stack or heap or const/global memory? so char* name="cherno"; here name is a constant char* type by default...? is my understanding correct? thanks in advance

[@monishkumardurairaj3038]

Thanks@Peterolen.......

[@ilyosbeknajmiddinov6754]

Hello, I have error initializing can't convert from const char[9] to char* could you help me !?

[@Highwind_]

const char * string = "String" is the same as declaring and initializing a const char array?

[@xrafter]

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

[@_adaldo]

I'd rather name this "Fantastic Strings and How to Use Them"

[@bikramjeet6536]

They should rightly be named so!! Using char ptrs was such a pain.

[@arnmazing3156]

Dang here I was hoping you would expand more on c-strings and how to manipulate them like using strstr(); or strcmp(); without using the string library

[@Nicolas-gq9vu]

Good work for this video!