Warnings in the build process / treat as errors

[tcptomato]

People are starting to commit code for which the compiler gives warnings. This can be dangerous as it might hide bugs, and could break the code in the future. The solution to this problem is the -Werror compiler flag, which treats warnings as errors.

This pull request shouldn't be merged atm, as it will break the build process. I created it more to start a discussion on this topic.

Changes.
Modified readme and the travis configuration file as to treat warnings as errors.

[WesleyCeraso]

Why do not merge? I think it should be to enforce the no-warning policy.

[tcptomato]

Because as is, it will break the build process. ( This is why Travis says the build for this commit failed :) )

[olajep]

Pushed compiler warning fixes. Can you rebase on master so we can see if it passes on travis too?

Thanks,
Ola

[tcptomato]

I rebased it on master. Which is 3 commits behind upstream/master. But when I add as a remote to get the changes, I get a permission denied on the git fetch. Gtg now, will debug later.

[tcptomato]

Added latest changes from upstream. See pull request #172