data[10] = {10,20,30,40,50,60,71,80,90,91}; The above is not correct (syntax error). It means you are assigning an array to data[10] which can hold just an element. If you want to initialize an array, try using Array Initializer: int[] data = {10,20,30,40,50,60,71,80,90,91}; // or int[] data; data = new int[] {10,20,30,40,50,60,71,80,90,91}; Notice the difference between the two … Read more
Basically copying and pasting from Bjarne Stroustrup’s “The C++ Programming Language 4th Edition”: List initialization does not allow narrowing (§iso.8.5.4). That is: An integer cannot be converted to another integer that cannot hold its value. For example, char to int is allowed, but not int to char. A floating-point value cannot be converted to another … Read more
In (ANSI) C99, you can use a designated initializer to initialize a structure: MY_TYPE a = { .flag = true, .value = 123, .stuff = 0.456 }; Other members are initialized as zero: “Omitted field members are implicitly initialized the same as objects that have static storage duration.” (https://gcc.gnu.org/onlinedocs/gcc/Designated-Inits.html)
The class declaration should be in the header file (Or in the source file if not shared). File: foo.h class foo { private: static int i; }; But the initialization should be in source file. File: foo.cpp int foo::i = 0; If the initialization is in the header file then each file that includes the … Read more
If your compiler supports C++11, you can simply do: std::vector<int> v = {1, 2, 3, 4}; This is available in GCC as of version 4.4. Unfortunately, VC++ 2010 seems to be lagging behind in this respect. Alternatively, the Boost.Assign library uses non-macro magic to allow the following: #include <boost/assign/list_of.hpp> … std::vector<int> v = boost::assign::list_of(1)(2)(3)(4); Or: … Read more
Use whatever you and your team find the most readable. Other answers have suggested that a new string is created every time you use “”. This is not true – due to string interning, it will be created either once per assembly or once per AppDomain (or possibly once for the whole process – not … Read more
There is a shorthand that I use that is not very time efficient, but fits on a single line: Set<String> h = new HashSet<>(Arrays.asList(“a”, “b”)); Again, this is not time efficient since you are constructing an array, converting to a list and using that list to create a set. When initializing static final sets I … Read more
Here’s the problem when I get too carried away with anonymous inner classes: 2009/05/27 16:35 1,602 DemoApp2$1.class 2009/05/27 16:35 1,976 DemoApp2$10.class 2009/05/27 16:35 1,919 DemoApp2$11.class 2009/05/27 16:35 2,404 DemoApp2$12.class 2009/05/27 16:35 1,197 DemoApp2$13.class /* snip */ 2009/05/27 16:35 1,953 DemoApp2$30.class 2009/05/27 16:35 1,910 DemoApp2$31.class 2009/05/27 16:35 2,007 DemoApp2$32.class 2009/05/27 16:35 926 DemoApp2$33$1$1.class 2009/05/27 16:35 4,104 … Read more
Let’s get pedantic, because there are differences that can actually affect your code’s behavior. Much of the following is taken from comments made to an “Old New Thing” article. Sometimes the memory returned by the new operator will be initialized, and sometimes it won’t depending on whether the type you’re newing up is a POD … Read more
Unless that value is 0 (in which case you can omit some part of the initializer and the corresponding elements will be initialized to 0), there’s no easy way. Don’t overlook the obvious solution, though: int myArray[10] = { 5, 5, 5, 5, 5, 5, 5, 5, 5, 5 }; Elements with missing values will … Read more