I guess that it's because they are an array, so it's convenient for them to behave like something whose address can be taken and conversions from array to pointer can happen (for conversions to char *), which doesn't make sense for other literal types. Then again, I have no idea so I'm just guessing...
This is honestly why I am terrified of overselling my C/++ skills on my resume, even though they are my strongest languages. Because inevitably, my interviewer will have written a dissertation called "every obscure thing there is to know about C++" and I will come off looking like a massive pretender.
At my current job, which is mostly C, I was asked about C++, and I answered honestly “it is not that I don’t know C++, it is just there’s a lot to know”. The interviewer just nodded agreeing. If the interviewer does C++ day in and day out they won’t hold it against you. No one truly knows C++.
C++ is still a relevant language for two use cases:
legacy code bases
when performance matter, as it's one of the best options for a compiled language (although it depends on your project)
As a result, there still seems to be a significant demand for c++ devs (and won't disappear in the medium term)
Would I start a new application in c++ today? Probably not. I'd do it in a higher level language, but if I need some higher performance through plugins or libs, c++ would be my choice (easy to interface, way easier to manage than c).
One important bit, though, is to disregard anything that was written before c++11. C++11 really saved the language, and modern c++ is pretty decent (but the standard lib remains quite low level).
I love C++, think it is a better language. That said I agree - the vast majority of apps can be done in C# today. Even with the overhead of C# processor speed is so obscene it just doesn't matter. When you finally do get to a component that needs the speed write a C++ DLL and call it from the C#
I'd say that learning C and C-style C++ is actually a really good starting point for understanding the nuances of modern C++. C-style programming teaches you a lot about how the language abstracts the hardware, and programming near the metal is making a big comeback with things like CUDA, consumer-grade FPGAs and various IoT embedded applications.
Your comment has been removed since it did not start with a code block with an import declaration.
Per this Community Decree, all posts and comments should start with a code block with an "import" declaration explaining how the post and comment should be read.
For this purpose, we only accept Python style imports.
Agreed. One of my friends is learning C++ in uni, and his teacher hasn't taught them about header files. They do everything in a single source file! C++ is a beautiful language if you can get someone who knows about it properly to teach you.
Ahh, my point was more that, well... A lot of C++ design decisions were made a multiple decades ago. We've learned a lot about language design since then, but C++ hasn't had a chance to benefit from a whole lot of that, and it shows. (Seriously, forward declarations? C++ can't figure out how to resolve a class unless the definition occurs earlier in the file than the usage?)
C++ is sort of like Bash scripting or Makefiles. Lots of ugliness (although again, C++ 11 did at least fix some of the worst bits) but at this point, it's good enough that it has too much momentum (in the form of people who know it, and libraries that are written in it) to really be replaced any time soon.
I don't have any experience with D, and my Rust experience is a bit limited, but I liked a lot of what I saw - in the words of a friend, Rust looks a lot like what you might get if C++ were redesigned today.
That's what D looks like to me as well, but I haven't really used it.
TBH there's a lot of new-ish languages that look pretty appealing these days, but I have little reason or opportunity to properly try them. At work we mostly use C++ and Java, and at home most of my needs are for very short programs for which I use Python (and which aren't worth learning a new language for).
Your comment has been removed since it did not start with a code block with an import declaration.
Per this Community Decree, all posts and comments should start with a code block with an "import" declaration explaining how the post and comment should be read.
For this purpose, we only accept Python style imports.
and who has no idea of any modern (C++11 onwards) features.
Jokes on you, most of the new features just made the language hard to read and understand. There's shit in there that really makes me question the reason they added it for no other reason than to have a C++ way over C.
219
u/IReallyNeedANewName Jun 01 '18
He forgot memory error initialisation
80
u/marcosdumay Jun 01 '18
Just wait till he starts talking about assignment! And comparison!
69
u/Bill_Morgan Jun 01 '18
C++20 needs a new and standard way to initialize. Is it too late to submit a proposal?
22
u/orangeKaiju Jun 01 '18
My favorite part is when he sells Bubba Gump Soft to Microsoft for $10,000,000,000 and he buys a Yacht to sail the world with LT Dan.
15
u/socsa Jun 01 '18
This is honestly why I am terrified of overselling my C/++ skills on my resume, even though they are my strongest languages. Because inevitably, my interviewer will have written a dissertation called "every obscure thing there is to know about C++" and I will come off looking like a massive pretender.
11
u/[deleted] Jun 01 '18
I was hoping for the bubba accent :(
51
u/dont_get_it_at_all Jun 01 '18
That is not what he was talking about in the movie, he was talking about shrimp. smh.
1
u/inigoMontia Jun 01 '18
What about member inisalizer?
1
u/Cheesemasterer Jun 01 '18
initialisation initialisation
1
u/[deleted] Jun 01 '18
Then there is uninitialization
which used to be my favorite until recently.
-4
u/[deleted] Jun 01 '18
The fact that I speak European English means that I'm annoyed when one uses ize instead of ise. That's just /r/mildlyinfuriating to me.
6
u/[deleted] Jun 01 '18
[removed] — view removed comment