3r33300. 3r3-31. Please do not read professional C /C ++ programmers).
 3r33300.
 3r33300. In the article, I express my point of view, if you disagree - justify in the comments.
 3r33300. The purpose of this article is to point out the shortcomings of C and C ++, which I really dislike and encourage you to use the new version of the language or maybe even offer some ideas for improving the standard.
 3r33300.
 3r33300. Well, it's time to rekindle the holivar.
 3r33300. 3r314. 3r3188.
 3r33300. I think everyone knows that it’s awesome strings in C ++. Especially if we are talking about the old type, in the new string a lot has been fixed and improved, but there is still no support for Unicode (!).
 3r33300.
 3r33300. In the standard C ++ 2? it seems like they are going to enter unicode strings.
 3r33300.
 3r33300. C ++ 20! And this is despite the fact that C ++ [b] exists since 1983 3r33282. .
 3r33300.
 3r33300. Open your favorite IDE and try to compile the following code:
 3r33300.
 3r33300.
#include
3r33300. #include
3r33300. 3r33300. int main ()
{
char string[256]; 3r33300. std :: cout "Hi:"; 3r33300. gets (string); 3r33300. std :: cout "Output:" string; 3r33300. return 0; 3r33300.}

 3r33300. UPD1: the commentator says that krakozyabry only on Windows. That's for sure, I forgot to write about it.
 3r33300. But still unpleasant.
 3r33300.
 3r33300. I compiled in Dev Cpp, the GCC compiler.
 3r33300.
 3r33300. Compile and see:
 3r33300.
 3r33300.  3r33300.
 3r33300. Good screen output, huh?
 3r33300.
 3r33300. Now let's replace the char string[256]on char * string.
 3r33300.
 3r33300. I’m not saying that this should work, but the compiler should have thrown the error out as a maximum.
 3r33300.
 3r33300. We got a work program that hung.
 3r33300. It would be better if the compiler threw an error.
 3r33300. And the whole garbage is that the compiler is not enough to compile it, it is not
 3r33300. brought a warning.
 3r33300.
 3r33300. Here's another joke:
 3r33300.
 3r33300.
#include
3r33300. using namespace std; 3r33300. int main () {
int arr[100]= {}; 3r33300. coutarr[101]endl; 3r33300. return 0; 3r33300.}

 3r33300. What do we expect? The compiler will tell us that it is impossible to refer to 101 array elements, since there are only 100 elements. But we compile, run and see 32765 (at least on my hardware).
 3r33300.
 3r33300. Hmm.
 3r33300.
 3r33300. Now let's test this code here:
 3r33300.
 3r33300.
int i = 5; 3r33300. i = ++ i + ++ i; 3r33300. std :: couti; 3r33300.
 3r33300. What do you think he will bring?
 3r33300.
 3r33300. The correct answer depends on the compiler.
 3r33300.
 3r33300. In GCC, this will be 1? but depending on the optimization flags.
 3r33300.
 3r33300. And in another compiler it can easily be 12
 3r33300.
 3r33300. I think everyone knows that in C and in the pluses a bunch of syntactic sugar, which is not always needed.
 3r33300.
 3r33300. For example, std :: cout4["string"]; This is the valid code
 3r33300. It outputs n, as well as std :: cout "string"[4];
 3r33300.
 3r33300. Great, huh?
 3r33300.
 3r33300. And now about the patient.
 3r33300. C ++ and network.
 3r33300. These are 2 sooo badly matched concepts.
 3r33300. Try to just download the image of the cat from your favorite site using the standard C ++ library.
 3r33300. This was not possible until the adoption of standard C ++ 17.
 3r33300. In the same standard library you cannot work with JSON.
 3r33300. Excellent comment about this.
 3r33300.

In general, working with JSON in C ++ is like a nightmare.
 3r33300.

3r3187. Source 3r3188. .
 3r33300. Do you think the condition will always be false?
 3r33300.
 3r33300.

    if (sizeof ('a')! = sizeof (char)) {
//do something
}
  

 3r33300. No, you are mistaken.
 3r33300.
 3r33300. If you compile it as a c ++ project, then the condition is likely to fail.
 3r33300. Should not.[1]
 3r33300. And if like a C project, then in that case sizeof ('a') == sizeof (int).
 3r33300. That's it.
 3r33300.[1]In general, many different C and C ++ compilers are also a problem.
 3r33300. Because a lot of solutions are non-standardized and they will work only in certain compilers.
 3r33300.
 3r33300. For example, 128 bit numbers in C ++. In gcc and clang there is a type __int12? while in Visual Studio it is not, because it is not a standard. Or, for example, strings in Visual Studio.
 3r33300.
 3r33300.

    String ^ MyString3 = "Hello, world!"; //try compiling into GCC

 3r33300. Or, for example, in the old Borland C ++ Builder, you can code written in Object Pascal.
 3r33300. And there are many such moments.
 3r33300.
 3r33300. Of particular pain is the lack of a list of C and C ++ packages.
 3r33300.
 3r33300. What follows from this? Use the new version of C ++, for example C ++ 17 and some problems will be solved.
 3r33300.
 3r33300. I must say that in the nearest competitor C ++ - Rust there are not most of the problems from this list, for example, there is a wonderful cargo, but of course it is not perfect either.
 3r33300.
 3r33300. And what problems C and C ++ do you know?
 3r33300. Write in the comments.
 3r33300.
 3r33300. UPD: Many people seem to have misunderstood my article:
 3r33300.
In no case do I want to criticize C /s ++ and say write on the plant.
 3r33300. Just pointing out the flaws in s /s ++, because they got a bit of themselves.
 3r33300. Everything has its drawbacks, I just shared my thoughts.
 3r33300. UPD2:
 3r33300.
 3r33300. In the comments, many people write that OS works this way and in general it is a feature. You guys are wrong.
 3r33300. The same proof that you can make a system programming language in which it is not so easy to shoot yourself in the foot.
 3r33300.
 3r33300. It’s just that C /C ++ is full of solutions that nobody can fix, because it can break backward compatibility.
 3r33300.
 3r33300. And yes, this is my opinion, it is  [b]  subjectively 3r33282. .
 3r33300.
 3r33300. If you do not agree - better comment, and not stupidly minus, because the opinion of all of us is
 3r33300. subjectively.
3r33300. 3r33300. 3r33300.
3r33300.
3r33300. 3r33300. 3r33300. 3r33300.