Wonders in the World of C++

[wondersofcpp]

Many meanings of static

static (without a class) is the private in C-land with respect to the linker. Extern is the public and it is the default.

src.cpp:

//not included in the object's symbol table //throws warnings if no one calls it static int foo() { return 42; } //default: other linked objects can call this method extern int bar() { return 1337; } //does not throw warning errors static inline int wohoo() { return 0; }

Don't be confused. Static in the context of a class does exaclty what you think it does.

[wondersofcpp]

How to initialize std::vector efficiently

If you need a vector of a fixed size and don't care about default initialization of your elements, don't do

std::vector<type> vectorname(num_elements); //O(n)

Instead do this:

std::vector<type> vectorname; vectorname.reserve(num_ekements) //O(1)

[wondersofcpp]

Prevent default constructors

Classname() = delete; Classname(const Classname &) = delete;

will make sure there's no default constructor or default copy constructor

[wondersofcpp]

fix 'multiple definitions of' by inlining

Linker is complaining about 'multiple definitions of ...' for your non-static method? Stackoverflow says you should inline it....

[wondersofcpp]

Python, is that you?

if( not( awesome or cool)) printf("Boo!");

Is valid C++

[wondersofcpp]

Ensuring that global functions in header files produce no duplicate symbol

Global functions don't care if there's #pragma once or #ifndef #def

Instead you have to use the inline keyword:

inline EvilGlobalFunction(){};

[wondersofcpp]

Using a templated function

never forget to write template before calling the function. clang is awesome enough to tell you that though.

object.template TemplatedFunction<T>(input, params);

[wondersofcpp]

Accessing the member variable of templated base class in the inheritanced class

In inheritanced class access the member_variable with

this->member_variable

http://stackoverflow.com/questions/14534316/use-of-undeclared-identifier-with-templates-and-inheritance-followup