Refactor the code according to the Google C++ Style Guide

[Yida-Lin]

#25

Standardize code style according to https://google.github.io/styleguide/cppguide.html.

Didn't have time to do functionality change, only style cleanup for now.

Note that some method name changes require the code changes in SigViewer as well.

[cbrnr]

Where does the style guide say that function names must be camel case?

[Yida-Lin]

@cbrnr I agree it looks a bit odd; it's not even camel case, it's Pascal case. It says it here: https://google.github.io/styleguide/cppguide.html#Function_Names

The C++ standard library does not adopt this style though http://www.cplusplus.com/reference/algorithm/

[cbrnr]

It's your decision. Coming mainly from Python this looks really weird.

[Yida-Lin]

@cbrnr By looking at this thread, looks like the snake_case() makes the most sense to me.

[cbrnr]

Yes, I'd go with the conventions used in the standard lib (at least for this case).

[Yida-Lin]

@cbrnr @tstenner think I cleaned up most stylistic things; most files changes in this PR are documentation changes auto generated by Doxygen, which you can ignore. Only xdf.h, xdf.cpp, and README.md are relevant.

[tstenner]

Personally, I prefer the LLVM over the Google style guide, but any style is an improvement over an inconsistent or undocumented style.

Two things: Having the compiled doxygen documentation in the repository adds a lot of noise to the commits. For liblsl, we use readthedocs to host the doxygen output so only the doxygen configuration files are in the repository. One other option is to include the doxygen output in the released archives so anyone downloading it has the html documentation.

The other things I'm missing is a clang-format file (labstreaminglayer example, interactive clang-format generator so that Visual Studio / QtCreator can automatically reformat the code according to the style guide.

[Yida-Lin]

@tstenner Thank you for your input, sounds great. I will look into these over the weekend.