Finally got around to answering this question, hope you guys enjoyed the video! What's the biggest issue you've had because someone stuck a using namespace somewhere?
First time i learned c++ the tutorial i watched the guy "using namespace std" and other namespaces, so i assumed it is ok. Couple of hours later, i actually added something like that in a header file, didnt mind. A bit later, everything broke. Needles to say i stopped doing this.
Tron I restrained from using it in a global scope, but I still use it in a local scope, because I don't see problems with that personally. But everyone has their own religion here.
In my algorithms class, the test runner that was supplied to the class had `using namespace std;` in the global scope in one of its header files, and as a result when I did the quicksort assignment I discovered minutes before the assignment was due that I'd actually been calling std::sort for everything when I'd been testing it earlier, rather than the function I'd written. Fortunately my sort function worked perfectly once I fixed that but it really could've been bad.
Im glad someone is finally addressing this. I've been helping people program in C++ for the last 5-6 years , and the one thing i notice is people always tend to use namespace std. There arent many tutorials that actually tell people not to use it because it could cause a lot of bloat. Ive actually was working with someone on a game, and it literally screwed with my custom vector class as well as custom map class.
I write a C++ program and broke every. Worst part is that I couldn't trace the issue at all and had to actually look on StackOverflow to realize that it was because of using namespace std.
I just want a list of ingredients that he puts in his latte. I want to talk that fast and type that fast and recall all the language details that fast. It must be the latte because something is giving him superhuman brain function!
Also I suggest that Cherno puts a few drops of his latte in the cactus plant every video. I suspect that the cactus will grow to be 6ft tall and form ears, eyes and a mouth and have an IQ of about 200. My IQ measured by Mensa is 145 but it could sure use a boost! lol
You know that you can write "using namespcae std" instead of writing std::, it will make a lot of the examples in this video clearer to read and understand.
but the using keyword is so situational it's not really worth it. It also becomes much less clear if you "using" more than one namespace. ...that was a pretty clunky sentence.
The only thing that you get by "using namespace std" are broken code samples which you have to go over and add std:: everywhere after you pasted the code.
That's not true. Any experienced c++ developer is completely familiar with anything inside the std namespace. The problem is with people (like he mentioned in the video) who try to replicate the STL and give it the exact names as the original. Yeah, that's gonna fuck everything up. There is absolutely no reason to std:: everywhere when you know what's what. All it does is unnecessarily bloat code. I'm not say don't not use it, but don't exaggerate it's limited consequences, which when they do arise, are easily solvable with any decent IDE.
The reason this question gets asked a lot is because programming courses don't want to have to explain scope and scope resolution early on, and once they do, using namespace std is so ingrained they don't bother undoing it.
True, it's same also in universities with fields not related to the programming directly. Like we have C++ course on our first year on mechanical engineering, and we were told write using_namespace as mandatory and never got explained what it actually is, because we always used to work with console output, never used more than 2 extensive libraries (vector and cmath) and nor wrote more than 800 lines of code. Thanks to the Cherno I've learned not to do it
Thankfully my teacher explained why using namespace std is not good on the second day of the class. Even though most of us don’t understand what he’s talking about at that time.
@@JoseGonzalez-rt5fk You can if you know for an absolute fact that the software will never be developed upon again after version 1. If it's for a customer; don't, you don't know what they're going to do in the future. If it's for your company; don't, you'll be the one that has to deal with it later because they wanted to use that one feature you need a lib for. If it's a personal project you might open source some day, also don't. Like there are very few cases where you could, but probably still shouldn't.
I'm kind of an old timer. Been programming since '81. I've even programmed on a computer with real magnetic core memory. You could open the box up and see each bit.......no joke..... In any case, you're one of the few TH-cam programmers I like. Keep up the good work.....
wow... would you say that programming was easier (or at least simpler) back then when the machines were less complicated and things were less abstract?
are you guys insane, today any 9 years old can download a radom App (for him) a radon tutorial on the internet and star programming on the get go, and in a couple of weeks he already know how to do lots of simples algorithms. back them you literally need to have electronics degree to understand whatever the fuck that maching were doing or else everything would break.
I dont know the basics of C++, I have zero programming knowledge and yet I understood what you were trying to tell. My mind is blown away by how great you are at teaching/explaining stuff to others! BEFORE ANYONE ASKS: I accidentally saved this video in my Watch Later and I was confused how/why it was there so I decided to check it(trying to figure out why i saved it) and then I was mesmerized by Cherno's excellent slow-mo coffee making and I just decided to stick till the end and wow I learned something great today.
We are in 2019 and your series still rocking. Your high quality videos and all the many advice you give are invaluable, because it is coming from years of practical experience in this industry. Keep up the good work.
Great job, I loved this video, it was very informative! I always try to follow best practices and I've been programming in C++ for about a month now. I am going to take your advice.
I'm newer to C++ and have thus far been using namespace std. I recognize the reasons why it isn't optimal to use it, however my rationale is that I want to get a hang of the syntax and function library before worrying about namespaces in general. It probably is about time to make the switch before my programs get too complex to keep track, though.
I wanted to add the addendum to this comment that I have since stopped using namespace std in my programs. It took about a week before it felt natural. For reference I'm usually coding about 30 minutes a day. It was worth switching, but I am glad I used it for my first few weeks of coding in C++. Stopping helped to develop a better understanding of scope, which becomes more important as your programs become more complex.
Really good, interesting video. I've only recently started learning C++ so this was something I've never even thought about. But why on earth do you think people who've clicked on a programming video would want to watch 2 minutes of you making a coffee first??
there are plenty of new programmer channels now, but yours is still my favourite number one, bc the others just brag about how great their life as software engineers is, while you offer valuable interesting content.
That is a good argument. Makes me think twice about using it. That being said, it will be an extremely long time if ever before I need to worry about massive files. No more namespace.
I know you probably know this but i just wanted to leave this out here because you can say "using std::(function name/ class name);" (ex. "using std::cout;"), i think this is better because you are just saying exactly what you want and it's easier because now if you want to for ex. to use another function from a namespace called "cout" you can actually see that there is already a "using std::cout;" so for this case i think that it is better plus you can actually see what functions/classes you are using from std(any namespace), again just becuase it's the best of both worlds dosen't mean you must use it, i just find it easier and better this way, and the rest is basically the same as Cherno, just wanted to say this, as he did not cover this.
Technically he does use namespace std. He details this in the video. He does so by explicitly declaring it each and every time he makes a call from std. What he doesn't do is obfuscate the use of namespaces by calling "using namespace std;" which is essentially the lazy way of doing so and can easily make it difficult to remember which function is being called from which namespace.
I thought it was going to be about slowing the program down to begin with given the extremely long intro but what he actually said makes much more sense
We can use namespace std before certain functions which uses the std library. While if we need to use a user-created library, we can just call it wherever required. Eg, std for regular keywords, and apple::(keyword) wherever needed.
I really like having complete knowledge and control over my types. Yes in theory if I don't import any other stl like classes I will know what I am working with, but I want to see it explicitly, and I also want to see it explicitly in 6 months. I also don't use auto much. I guess this also comes down to what you work on and your role in the team. I do a lot of reverse engineering and often think about actual individual bits of data. I am often also the guy that they call when something "should work but it doesn't" and it's always some small detail like a bug in a private method. Abstraction and short code are great, but some of us have to dive into the ugly details so making everything explicit became a habit of mine.
You should post more these type of concept videos ,i was about to go to bed and after watching this well my sleep is been chased away .It was good and thank u
The std library is often not really fit to use in low level engine programming because you need performance, thread safety, memory leak safety etc. pp. Creating your own std library that mimics the actual std library but is better for your purposes ist quite common actually.
@@PoojaDeshpande84 The EASTL is publicly available on GitHub, and code that handles DLC wouldn't be defined there. I get that you're trying to knock EA here, but at least say something that makes sense.
Interesting. It's like the fact that I prefer to code in my native language (french) so I don't mix my functions (in french) and more general functions (in english).
Good to see someone has basically the same view I do when it comes to name spaces. I'd probably used vector as an example you have std::vector and then you can have math and graphic libraries with vectors which are entirely different in nature. When I first stared using C++ the std wasn't near as good as it is now. It was pretty easy to write better performing code on your own. So people very often created their own versions of what was in std. 99.9% of the time I don't use it. The times I do it is usually something short that is being made and I probably just had the default code system create a console project and was to lazy to delete it to simply show someone else how something works. For large projects I never use it.
I've been programming in C++ since before namespaces existed . Using "using namespace std" was something I latched onto pretty quickly when namespaces first became a thing and it hasn't ever confused me before, nor has it ever confused anyone working with my code. I guess it's just a matter of style. So my question is, when you are using functions from eastl, are you also using functions from std simultaneously? You mentioned that eastl is an API replacement for std, so I would expect one would only use one without the other.
Watched half, didn't even need to finish, I was sold on not using namespace in like video three lol, so I was already convinced before this video. Great work Cherno.
Good point. Who knows what may happen if you were "using namespace std;" and "using namespace eastl;" and called a function, that was included in both, but varied slightly in definition.
Hey man. There are folks whining about the intro. Don’t listen to them, they are brilliant because you’re not just a robot teaching us code. We want to know you as a person in ways you’ll want us to. Heck, throw in some drone footage of yer homeland Australia, We’ll love it.😍 Soo.. thank you so much, you taught me a lot of good programming practices. Cheers
People come here to learn C++. They find a high quality video and class FOR FREE and still complain about seconds of coffee making intro. Those shouldn't be here then.
Heavily disagree. Because like any naming convention, whether “using namespace std;” makes code easier or harder to read depends entirely on your code. Just like in actual language, btw. If you were to stick to your guts you’d use punctuation and capitalization. You don’t, because implying proper qualification of your sentences is enough to be understood. Just like implying proper qualification of functions is often enough for code to be understandable.
I agree its context dependent. If I were to be showcasing a piece of code on a slideshow, I would use this expression. But for any professional codebase or project, I would never use this. And most would agree with me on this.
Simon Dimas no need to be rude. You could express the same sentiment saying something like ”Thanks for the videos. That intro was a bit long and doesn’t really relate to the content. Keep up the gopd work!” By the way, I liked it as a one off thing but it would get tiresome if it was in every video.
Why is it so ubiquitous in school to use namespace std in the header ? It seems like not very useful to learn something that should be avoided at all costs when using the :: syntax actually teaches you how namespaces work
Or you just don't complain about it and let him do what he wants with his skills / free time, I am sick of people saying "Im here for the this", if you don't like it. Go else where for you C++ videos.... Oh wait, they are all terrible so I guess you can either give him props or complain and watch it anyway lol. Because lets be honest, you are going to watch them anyway...
I can see your point here. There have been times when I revisited code after a month. If there was any ambiguity... Oh man... I've had to rewrite code and double down on documentation. I totally see where you are coming from.
I mean, the whole point of having namespaces was for name resolution. It's so that we know where certain symbols come from. What's the point of having that feature in the language if people are just going to refuse to use it?
@@NyscanRohid if you use "using namespace std" at the head of your code, and you have a similarly named function in another namespace, then you are not going to be using namespace to make your code more clear. If you use namespaces then use them correctly, but not with std and not when there could be ambiguity, otherwise you'll muddy your code up. That's what he's saying
@@MrJdcirbo No, that's what I said. I'm agreeing with him. When you use `using namespace std;` you're not actually _using_ the namespace, you're just obscuring it in your code. Yeah, you say that you're `using` namespace std, but are you really _using_ it, or are you _misusing_ it?
this is very important lesson, especially if you ever need to maintain or update that code. it's near imossible to remember how your code works after eg. 6 months, let alone how many hours and googling and stackoverflow posts reading goes then to figure out why this funny runtime code abnormality. very well presented lesson.
Ty for that, I all the time using namespace std and I didnt know there would be some situations where using that would be a problem, it's good to be aware of that.
I'll admit that there are projects where this matters, but I've been going for a long time now and haven't burnt myself yet. So I think I can hold out on changing like, a hundred header files for a little longer.
I just think that since your channel is dedicated to helping people understand coding, it'd be much easier for us newbies to read when there aren't a million std:: everywhere... yeah maybe to you it looks cleaner the other way but not all of us are as good as you :P food for thought
I guess it depends on your environment. If your IDE shows you information about functions as you type them or select them (yours appear to not do that), then that removes a lot of the confusion. It can show both which namespace the function belongs to, which parameters it takes, and most crucially it can show that there are several functions available with the same name. I would also say that if you're going to include "use namespace std", then you should stay consistent and do it in every file. Even when it's not included, assume that it is there, and don't include some other namespace with a function like find_if or print. That way you know that if you ever see "print" without a prefix, you can be certain that it's std::print. Same thing if you're in the other camp and want to avoid "use namespace X", then I see absolutely no reason why you should accept it for namespaces with longer names. It's much better to be consistent and use an alias to shorten the name: "namespace rlns = ::reallylongnamespace"
I was wondering that same question every since I first watched your videos. Yeah, when I first found out "using namespace std" I really thought it was the best thing in the world. But your point is surprisingly compelling. Makes me think that if I ever intended to make a complex code library with more than a handful of classes I should actively try to understand and use namespaces to segregate classes.
I used to think "there's 0 possible reason to not use namespace std because it reduces so much clutter and even in a short program tens of std::cout and std::endl" but then I was thinking that many times I also write programs that have maybe one output print. And I was thinking it possibly adds some unnecessary amount of junk in compiling the code (maybe not) so I maybe shouldn't use it without exception. And now hearing this it all makes sense, especially having used many python libraries and considering the possibility that they might become part of me using C++ as well, the non-standard libraries.
Finally got around to answering this question, hope you guys enjoyed the video!
What's the biggest issue you've had because someone stuck a using namespace somewhere?
First time i learned c++ the tutorial i watched the guy "using namespace std" and other namespaces, so i assumed it is ok. Couple of hours later, i actually added something like that in a header file, didnt mind. A bit later, everything broke. Needles to say i stopped doing this.
Tron I restrained from using it in a global scope, but I still use it in a local scope, because I don't see problems with that personally. But everyone has their own religion here.
In my algorithms class, the test runner that was supplied to the class had `using namespace std;` in the global scope in one of its header files, and as a result when I did the quicksort assignment I discovered minutes before the assignment was due that I'd actually been calling std::sort for everything when I'd been testing it earlier, rather than the function I'd written. Fortunately my sort function worked perfectly once I fixed that but it really could've been bad.
Im glad someone is finally addressing this. I've been helping people program in C++ for the last 5-6 years , and the one thing i notice is people always tend to use namespace std. There arent many tutorials that actually tell people not to use it because it could cause a lot of bloat. Ive actually was working with someone on a game, and it literally screwed with my custom vector class as well as custom map class.
I write a C++ program and broke every. Worst part is that I couldn't trace the issue at all and had to actually look on StackOverflow to realize that it was because of using namespace std.
When he says "never ever, EVER, use namespace in a header file" you can see the culmination of several hours of debugging agony in his eyes.
Thats solid advice. I can feel it.
My college does all the time lol
@@AviPars ur college should be in hell rn tbh
Zooming into those eyes and flashing through a thousand memories from 2am would've been a masterful edit for sure.
There a guys who start their video with an ad. And there is cherno, who shows how to make coffee in slowmo instead
Excuse me , but obviously his name is "A Jenner" according to (closed caption).Better to use subtitle options (CC button over there).
As someone who has never before heard about this channel, I was very confused
I just want a list of ingredients that he puts in his latte. I want to talk that fast and type that fast and recall all the language details that fast. It must be the latte because something is giving him superhuman brain function!
Also I suggest that Cherno puts a few drops of his latte in the cactus plant every video. I suspect that the cactus will grow to be 6ft tall and form ears, eyes and a mouth and have an IQ of about 200. My IQ measured by Mensa is 145 but it could sure use a boost! lol
ward
You know that you can write "using namespcae std" instead of writing std::, it will make a lot of the examples in this video clearer to read and understand.
but the using keyword is so situational it's not really worth it. It also becomes much less clear if you "using" more than one namespace.
...that was a pretty clunky sentence.
The only thing that you get by "using namespace std" are broken code samples which you have to go over and add std:: everywhere after you pasted the code.
It was a joke xD
That's not true. Any experienced c++ developer is completely familiar with anything inside the std namespace. The problem is with people (like he mentioned in the video) who try to replicate the STL and give it the exact names as the original. Yeah, that's gonna fuck everything up. There is absolutely no reason to std:: everywhere when you know what's what. All it does is unnecessarily bloat code. I'm not say don't not use it, but don't exaggerate it's limited consequences, which when they do arise, are easily solvable with any decent IDE.
I use condoms. So there.
The reason this question gets asked a lot is because programming courses don't want to have to explain scope and scope resolution early on, and once they do, using namespace std is so ingrained they don't bother undoing it.
Great observation!
That shit happened to me when I started lol
My teacher didn’t even know about unique scope name resolution lol. They’re too caught up in C World.
True, it's same also in universities with fields not related to the programming directly. Like we have C++ course on our first year on mechanical engineering, and we were told write using_namespace as mandatory and never got explained what it actually is, because we always used to work with console output, never used more than 2 extensive libraries (vector and cmath) and nor wrote more than 800 lines of code. Thanks to the Cherno I've learned not to do it
Thankfully my teacher explained why using namespace std is not good on the second day of the class. Even though most of us don’t understand what he’s talking about at that time.
“Never EVER use ‘using namespace’ in a header file. “ Noted.
Learned this the hard way
You can if you don't use other libraries like he does, it would save you a bit of time. Although, it would raise a bad habit.
If you in contest about Algorithm (like ACM ICPC, ...) then you should use "using namespace std", else you shouldn't use it.
@@JoseGonzalez-rt5fk You can if you know for an absolute fact that the software will never be developed upon again after version 1. If it's for a customer; don't, you don't know what they're going to do in the future.
If it's for your company; don't, you'll be the one that has to deal with it later because they wanted to use that one feature you need a lib for.
If it's a personal project you might open source some day, also don't.
Like there are very few cases where you could, but probably still shouldn't.
Ok, but did you understand why?
You don't have to bring the entire std namespace. I mostly use:
using std::cout;
using std::endl;
and using std:cin;
lol didnt even know I could do that...
new to c++
You probably shouldn't use std::endl much at all
@@DarkLevis I mean, if you're just outputting variables or something, it's easier than typing '
'. What's wrong with endl?
@@zeyode nothing horribly wrong just it calls std::flush after '
' which is often not intended.
“Remove all the STDs.”
Dude! Your videos are highly appreciated. I'm a CS student and I find your "real world" perspective on things to be extremely helpful.
I'm kind of an old timer. Been programming since '81. I've even programmed on a computer with real magnetic core memory. You could open the box up and see each bit.......no joke..... In any case, you're one of the few TH-cam programmers I like. Keep up the good work.....
Wow, I first played with QBASIC, Assembly, etc in 1993 and I thought those were the old days. Lol. Makes me feel young. ;)
I envy y'all early programmers. You had it cooler back then
@@_lapys ikr, people that time had less resources to learn from, i respect old programmers, they r rly hardworking
wow...
would you say that programming was easier (or at least simpler) back then when the machines were less complicated and things were less abstract?
are you guys insane, today any 9 years old can download a radom App (for him) a radon tutorial on the internet and star programming on the get go, and in a couple of weeks he already know how to do lots of simples algorithms.
back them you literally need to have electronics degree to understand whatever the fuck that maching were doing or else everything would break.
Why I don't "using namespace std"
"latte art could use a bit of work but really hits the spot"
-TheCherno
Will read your comment while he said that.
I dont know the basics of C++, I have zero programming knowledge and yet I understood what you were trying to tell. My mind is blown away by how great you are at teaching/explaining stuff to others!
BEFORE ANYONE ASKS: I accidentally saved this video in my Watch Later and I was confused how/why it was there so I decided to check it(trying to figure out why i saved it) and then I was mesmerized by Cherno's excellent slow-mo coffee making and I just decided to stick till the end and wow I learned something great today.
TH-cam is a strange place
Now we all know where the Patreon money is going towards lmao.
Probably his EA money to be fair
Going to Costa Rica cofee plantations
Making good content ?
"What you may have noticed at the beginning of this video"
You making coffee?
longest. intro. ever.
This guy clearly does not listen to Pink Floyd.
@@IsakFyksen lol
best. intro. ever.
Yeah but i loved every second of it
so you are new here
We are in 2019 and your series still rocking. Your high quality videos and all the many advice you give are invaluable, because it is coming from years of practical experience in this industry. Keep up the good work.
2020 :)
2021, still top tier
2022!
2023...
2024..🚀🔥
Great job, I loved this video, it was very informative! I always try to follow best practices and I've been programming in C++ for about a month now. I am going to take your advice.
The same with me too. Very new to C++ (3 wks now). I like this very channel. Already learning a lot. A big thanks to @TheCherno for his great job.
this video starts with 2 minutes of making coffee
I'm newer to C++ and have thus far been using namespace std. I recognize the reasons why it isn't optimal to use it, however my rationale is that I want to get a hang of the syntax and function library before worrying about namespaces in general. It probably is about time to make the switch before my programs get too complex to keep track, though.
I wanted to add the addendum to this comment that I have since stopped using namespace std in my programs. It took about a week before it felt natural. For reference I'm usually coding about 30 minutes a day. It was worth switching, but I am glad I used it for my first few weeks of coding in C++. Stopping helped to develop a better understanding of scope, which becomes more important as your programs become more complex.
I am also new to C++ , and searching for people to join me on discord to build a small community to share knowledge and help newbies.
@@laveeshtomar I am interested in talking to other aspiring programmers. Feel free to post the discord link when it's up!
That intro was one of the most cleanest, beautiful things I have ever seen. Well done, man!
wtf man the last time i watched you it was you talking over visual studio now you out here being a videography pro
I was like: "GASP!" when he waved the mug around the laptop!
someone here has ptsd because of accidents with coffee. I understand you perfectly :p
@@dionyzus2909 My dad spilled a drink on his laptop keyboard. it was instantly dead.
Really good, interesting video. I've only recently started learning C++ so this was something I've never even thought about. But why on earth do you think people who've clicked on a programming video would want to watch 2 minutes of you making a coffee first??
Hey, you know you can just using namespace std; and then you don't have to type std everytime
I'll sneak into your codebase and add "#define eastl:: std::"
You're like hitler, but even hitler cared about Germany or something
@@kylecox5127 lol
Then suddenly all EA games will become free and slower xD
(IDK if that makes sense or not. all I am saying is EAAAAAA = PAYYY and stdlib = slow lib!!)
@@kylecox5127 Lol nice reference
monster :0
there are plenty of new programmer channels now, but yours is still my favourite number one, bc the others just brag about how great their life as software engineers is, while you offer valuable interesting content.
That is a good argument. Makes me think twice about using it.
That being said, it will be an extremely long time if ever before I need to worry about massive files. No more namespace.
I was waiting for this video from quite some time and now wait is over. Really good video !!!. Thanks
I know you probably know this but i just wanted to leave this out here because you can say "using std::(function name/ class name);" (ex. "using std::cout;"), i think this is better because you are just saying exactly what you want and it's easier because now if you want to for ex. to use another function from a namespace called "cout" you can actually see that there is already a "using std::cout;" so for this case i think that it is better plus you can actually see what functions/classes you are using from std(any namespace), again just becuase it's the best of both worlds dosen't mean you must use it, i just find it easier and better this way, and the rest is basically the same as Cherno, just wanted to say this, as he did not cover this.
These intros are the cherry on top of the cream on top of the cake. Beautiful content in every sense.
That intro was oddly mesmerizing
This is 2021November, a bit late....but your coffee /latey making procedure is both calming and mesmerizing...good start for a vid!
Sorry, I have a question. Why don't you use namespace std?
Yeah, and also, what programming ide is this?
Visual studio 2017
Technically he does use namespace std. He details this in the video. He does so by explicitly declaring it each and every time he makes a call from std. What he doesn't do is obfuscate the use of namespaces by calling "using namespace std;" which is essentially the lazy way of doing so and can easily make it difficult to remember which function is being called from which namespace.
Nice name tho...
Thanks a lot.
Thanks for the tip on the header. I haven’t experienced any issues because of that but I can see how that would be disastrous in a group setting
Lol, love it... more and more of Peter McKinnon :) Keep it going!
I thought it was going to be about slowing the program down to begin with given the extremely long intro
but what he actually said makes much more sense
What I was always told was it ok to use in main and no where else but I think I might stop doing even that
Fantastic intro, mate!
Is that a coffee or a milkshake?
mean mole It is a latte. Basically a fancy steamed coffee milkshake.
Hard to call it a milkshake when it's not cold or made with icecream. It's simply a cafe latte, espresso + steamed milk.
@@warrick_lo Very brave.
We can use namespace std before certain functions which uses the std library. While if we need to use a user-created library, we can just call it wherever required. Eg, std for regular keywords, and apple::(keyword) wherever needed.
I really like having complete knowledge and control over my types. Yes in theory if I don't import any other stl like classes I will know what I am working with, but I want to see it explicitly, and I also want to see it explicitly in 6 months. I also don't use auto much.
I guess this also comes down to what you work on and your role in the team. I do a lot of reverse engineering and often think about actual individual bits of data. I am often also the guy that they call when something "should work but it doesn't" and it's always some small detail like a bug in a private method. Abstraction and short code are great, but some of us have to dive into the ugly details so making everything explicit became a habit of mine.
You should post more these type of concept videos ,i was about to go to bed and after watching this well my sleep is been chased away .It was good and thank u
I think the better question is why does EA have their own Standard library?
The std library is often not really fit to use in low level engine programming because you need performance, thread safety, memory leak safety etc. pp.
Creating your own std library that mimics the actual std library but is better for your purposes ist quite common actually.
they need to hide the code where they fleece the customers with dumb dlc
@@PoojaDeshpande84 The EASTL is publicly available on GitHub, and code that handles DLC wouldn't be defined there. I get that you're trying to knock EA here, but at least say something that makes sense.
Bc Std::vector is not very well optimised
Bro this video is literally the reason I got my internship. All the good wishes and power in the world to you Cherno
At least he knows the important of a good espresso before anything is said.
The intro honestly adds so much to the video even though it has nothing to do with namespaces.
I thought I accidentally clicked on video about coffee
Very nicely explained. And other than that video editing and intro section was also nice.
Thank You.
Interesting. It's like the fact that I prefer to code in my native language (french) so I don't mix my functions (in french) and more general functions (in english).
I am laughing so hard on the intro
Welcome back to my Coffee++ Series, my name is Cherno
Good to see someone has basically the same view I do when it comes to name spaces.
I'd probably used vector as an example you have std::vector and then you can have math and graphic libraries with vectors which are entirely different in nature.
When I first stared using C++ the std wasn't near as good as it is now. It was pretty easy to write better performing code on your own. So people very often created their own versions of what was in std.
99.9% of the time I don't use it. The times I do it is usually something short that is being made and I probably just had the default code system create a console project and was to lazy to delete it to simply show someone else how something works. For large projects I never use it.
Lovely intro
lovely topic
and best video
in the TH-cam i have ever seen
Keep going..(:
Hold on!
..I need to watch this with a coffee. Brb.
Mate..what a great content! Thx for the explanation!
Well there it is, one of the examples what separates good coders with lousy ones.
Imagine not using namespace std
adorable intro and as always your explanation made it more easier to understand :) ; Enjoyed it ;
First two minutes of the video == using namespace std;
Skyclad lol.
A whole two minutes of dramatic coffee making vibes.
Fantastic video.
I've been programming in C++ since before namespaces existed . Using "using namespace std" was something I latched onto pretty quickly when namespaces first became a thing and it hasn't ever confused me before, nor has it ever confused anyone working with my code. I guess it's just a matter of style.
So my question is, when you are using functions from eastl, are you also using functions from std simultaneously? You mentioned that eastl is an API replacement for std, so I would expect one would only use one without the other.
Watched half, didn't even need to finish, I was sold on not using namespace in like video three lol, so I was already convinced before this video. Great work Cherno.
Then there’s Rust.
#[macro_use] // I think that’s the syntax.
extern crate clap;
use clap::*; // oof.
Derp Marine i think if you have clap in your Cargo.toml then you only have to:
use clap::*;
Good point. Who knows what may happen if you were "using namespace std;" and "using namespace eastl;" and called a function, that was included in both, but varied slightly in definition.
that intro tho
GAGE was long.
Very well explained! Thanks for the tip about using a namespace!
I'm a simple man, I get a youtube notification when Cherno uploaded a new video, I hit like.
You are so simple, you can't even come up with an original comment.
My biggest catastrophe with "using namespace" so far was not finding The Cherno's channel earlier
Hey man. There are folks whining about the intro. Don’t listen to them, they are brilliant because you’re not just a robot teaching us code. We want to know you as a person in ways you’ll want us to.
Heck, throw in some drone footage of yer homeland Australia, We’ll love it.😍
Soo.. thank you so much, you taught me a lot of good programming practices.
Cheers
People come here to learn C++. They find a high quality video and class FOR FREE and still complain about seconds of coffee making intro. Those shouldn't be here then.
Everything I wanted to know...... but didn't know enough to ask an intelligent question. THANK YOU..... SUBSCRIBED!!!
What's the point of the long intro?
slap_my_hand porn
He probably bought an expensive dslr and doesn't do much with it so he needs to make long intros to justify getting the camera
It's art. Art is the point of art.
+slap_my_hand Coffee is like 80% of coding, Its a coding tuturial.
Whats the point on asking whats the point of the long intro?
I've liked it after intro because of nice coffee making scene... and about C++ it is as good as always! Great job!
Myself and most professionals don't because of name conflicts
Another great video. Never looked at it that way! Thank you!
Nice intro but WHY SO MUCH CREAM
because it's a latte
the random edit energy sometimes lol. They're pretty nicely done. Can't program without coffee after all
Using std:: actually makes your code cleaner
It's and it prevents sudden headaches!!
Depends you could use it in function context and make a rule that you never use it in global context
You have a really good point, usually explicit code looks a little bit more bloated, but is much more readable!
using namespace std
at the top of the program violates the reason why namespaces were added in the language.
0:10 roflol, is that your daily coffee ration? Reminds me so much of Seattle where the people drink coffee like trucks drink gas.
6:36 i laughed so hard
You've convinced me! Excellent video.
"using namespace std;"
ahh the mark of an amateur
Karan Lobana could not agree more
Heavily disagree. Because like any naming convention, whether “using namespace std;” makes code easier or harder to read depends entirely on your code.
Just like in actual language, btw. If you were to stick to your guts you’d use punctuation and capitalization. You don’t, because implying proper qualification of your sentences is enough to be understood. Just like implying proper qualification of functions is often enough for code to be understandable.
It’s like the mall grabbing of the coder world.
I agree its context dependent. If I were to be showcasing a piece of code on a slideshow, I would use this expression. But for any professional codebase or project, I would never use this. And most would agree with me on this.
Ah yes, the mark of code that will never see the light of day :)
I am watching this at morning and the intro... I didn't had a coffee
Hands down one of the most pointless intro I've ever seen.
Simon Dimas no need to be rude. You could express the same sentiment saying something like ”Thanks for the videos. That intro was a bit long and doesn’t really relate to the content. Keep up the gopd work!”
By the way, I liked it as a one off thing but it would get tiresome if it was in every video.
@@martinlarsson8947 Whip anf naenae
Why is it so ubiquitous in school to use namespace std in the header ? It seems like not very useful to learn something that should be avoided at all costs when using the :: syntax actually teaches you how namespaces work
I hate these way too long intros
SteakieFrags same, seem pretty pointless for coding vids
Every time i see that i wanna click away from the video.
I think his other passion is videography, so be supportive ;-)
Toxicity Game Dev He would be able to create another channel for that.
Or you just don't complain about it and let him do what he wants with his skills / free time, I am sick of people saying "Im here for the this", if you don't like it. Go else where for you C++ videos.... Oh wait, they are all terrible so I guess you can either give him props or complain and watch it anyway lol. Because lets be honest, you are going to watch them anyway...
The most comforting intro ever
I can see your point here. There have been times when I revisited code after a month. If there was any ambiguity... Oh man... I've had to rewrite code and double down on documentation. I totally see where you are coming from.
I mean, the whole point of having namespaces was for name resolution. It's so that we know where certain symbols come from. What's the point of having that feature in the language if people are just going to refuse to use it?
@@NyscanRohid if you use "using namespace std" at the head of your code, and you have a similarly named function in another namespace, then you are not going to be using namespace to make your code more clear. If you use namespaces then use them correctly, but not with std and not when there could be ambiguity, otherwise you'll muddy your code up. That's what he's saying
@@MrJdcirbo No, that's what I said. I'm agreeing with him. When you use `using namespace std;` you're not actually _using_ the namespace, you're just obscuring it in your code. Yeah, you say that you're `using` namespace std, but are you really _using_ it, or are you _misusing_ it?
@@NyscanRohid I misunderstood. I apologize. I'm so used to arguing in these comment sections. Does that say something about me or society?... Or both?
Great explained. Thanks!
Dude, new C++ programmer. Your channel is gold. I wish you were my friend.
me too.
You're a better C++ teacher than any of my C++ professors.
this is very important lesson, especially if you ever need to maintain or update that code. it's near imossible to remember how your code works after eg. 6 months, let alone how many hours and googling and stackoverflow posts reading goes then to figure out why this funny runtime code abnormality. very well presented lesson.
Ty for that, I all the time using namespace std and I didnt know there would be some situations where using that would be a problem, it's good to be aware of that.
I'll admit that there are projects where this matters, but I've been going for a long time now and haven't burnt myself yet. So I think I can hold out on changing like, a hundred header files for a little longer.
I just think that since your channel is dedicated to helping people understand coding, it'd be much easier for us newbies to read when there aren't a million std:: everywhere... yeah maybe to you it looks cleaner the other way but not all of us are as good as you :P food for thought
Thanks for clearing the confusion
I guess it depends on your environment. If your IDE shows you information about functions as you type them or select them (yours appear to not do that), then that removes a lot of the confusion. It can show both which namespace the function belongs to, which parameters it takes, and most crucially it can show that there are several functions available with the same name.
I would also say that if you're going to include "use namespace std", then you should stay consistent and do it in every file. Even when it's not included, assume that it is there, and don't include some other namespace with a function like find_if or print. That way you know that if you ever see "print" without a prefix, you can be certain that it's std::print.
Same thing if you're in the other camp and want to avoid "use namespace X", then I see absolutely no reason why you should accept it for namespaces with longer names. It's much better to be consistent and use an alias to shorten the name: "namespace rlns = ::reallylongnamespace"
I think for halloween my costume is going to be a header file that uses namespaces.
I was wondering that same question every since I first watched your videos. Yeah, when I first found out "using namespace std" I really thought it was the best thing in the world. But your point is surprisingly compelling. Makes me think that if I ever intended to make a complex code library with more than a handful of classes I should actively try to understand and use namespaces to segregate classes.
Came for the programming lesson. Stayed for the slow-motion latte art.
I used to think "there's 0 possible reason to not use namespace std because it reduces so much clutter and even in a short program tens of std::cout and std::endl" but then I was thinking that many times I also write programs that have maybe one output print. And I was thinking it possibly adds some unnecessary amount of junk in compiling the code (maybe not) so I maybe shouldn't use it without exception. And now hearing this it all makes sense, especially having used many python libraries and considering the possibility that they might become part of me using C++ as well, the non-standard libraries.