standards

I'm reading the MDN javascript reference , accordingly the following code no longer returns false : function haveES6DuplicatePropertySemantics(){ "use strict"; try { ({ prop: 1, prop: 2 }); // No error thrown, duplicate property names allowed in strict mode return true; } catch (e) { // Error thrown, duplicates prohibited in strict mode return false; } } In ECMAScript 5 strict mode code, duplicate property names were considered a SyntaxError. With the introduction of computed property names making duplication possible at runtime, ECMAScript 6 has removed this restriction. My question is, what

When I use new[] to create an array of my classes: int count = 10; A *arr = new A[count]; I see that it calls a default constructor of A count times. As a result arr has count initialized objects of type A . But if I use the same thing to construct an int array: int *arr2 = new int[count]; it is not initialized. All values are something like -842150451 though default constructor of int assignes its value to 0 . Why is there so different behavior? Does a default constructor not called only for built-in types? sharptooth See the accepted answer to a very similar question . When you use new[]

I'm playing around with gmock and noticed it contains this line: #include <tuple> I would have expected tuple.h . When is it okay to exclude the extension, and does it give the directive a different meaning? Michael Burr The C++ standard headers do not have a ".h" suffix. I believe the reason is that there were many, different pre-standard implementations that the standard would break. So instead of requiring that vendors change their exiting "iostream.h" (for example) header to be standards compliant (which would break their existing user's code), the standards committee decided that they'd