Why was it is not an easy question. Maybe it’s time to ask the standard committee why were they as crazy as to standardize (the now removed) gets() function as well? Sometimes, the standard is simply brain-dead, whether we want it or not. The first C was not today’s C. It was not “designed” to … Read more
It’s actually the statement after the one you mark as causing the program to crash that causes the program to crash! You must pass the same pointer to delete[] as you get back from new[]. Otherwise the behaviour of the program is undefined.
My guess is that it is a problem with the compiler options you are using, the compiler itself, or the file system. I just now compiled both versions (with optimizations on) and ran them against a 92,000 line text file: c++ version: 113 ms c version: 179 ms And I suspect that the reason that … Read more
I received the error “A suitable constructor for type ‘<type>’ could not be located.” after accidentally generating a protected constructor instead of public constructor. Marking it back to public fixed it.
There’s a certain amount of misinformation here: “The default access modifier is not private but internal” Well, that depends on what you’re talking about. For members of a type, it’s private. For top-level types themselves, it’s internal. “Private is only the default for methods on a type” No, it’s the default for all members of … Read more
string.Join(“, “, Array.ConvertAll(somelist.ToArray(), i => i.ToString()))
You can create a new instance of date with the seconds set to 0. DateTime a = DateTime.UtcNow; DateTime b = new DateTime(a.Year, a.Month, a.Day, a.Hour, a.Minute, 0, a.Kind); Console.WriteLine(a); Console.WriteLine(b);
If you want to selectively hide functions from B it does not make much sense to use public inheritance in the first place. Use private inheritance & selectively bring methods from B into the scope of A: struct B{ void method1(){}; void method2(){}; }; struct A : private B{ using B::method1; }; A a; a.method1(); … Read more
void Foo() { throw new OutOfMemoryException(); } :)))
D and Go will probably just become as popular as Python and Ruby are today. They each fill a niche, and even though D was supposed to be a full-fledged replacement of C++, it probably will never acquire enough mass to push C++ away. Not to mention that they both aren’t stable/mature enough, and it’s … Read more