Conversation
It builds on my env. Trying to workaround the travis "no gcc 4.8"-bug as you mentioned on the ML, |
references should never be null, actuall code does not compile under clang 3.6 that enforces that please review
Conflicts: src/main/engine/Input.cpp src/test/testeverything/engine/InputTest.cpp
This reverts commit c3307fe.
@rhyolight the gcc failure seems to be that |
the OSX issue (missing std::move() in libstdc++ shipped on Mac) |
Otherwise, the automated changes to c++ should be more or less stable and are eagerly waiting for your reviews 😈 |
to fix problems with c++11, std::move missing for example
flagging this 'help wanted', I'd need someone with OSX to test the right |
@breznak said:
The reason is that the default gcc tool chain on the machine is |
That's great, @scottpurdy. Thanks for jumping in. |
Include yaml-cpp
Please see breznak#1 to get this up to par with OS X |
You're so quick! |
I'm ⌚ ing you :-D |
And we're 🍏 |
👍 Thanks, everyone! |
👏 |
This reverts commit 8ab6254. Conflicts: .travis.yml src/main/test/Tester.cpp src/test/testeverything/TestEverythingMain.cpp src/test/unit/test/TesterTest.hpp
Fixing skipped unit tests - random, solving issue numenta#177
1/ set -std=c++11 flag
2/ verify in travis env
3/ transform code with clang-modernize
EDIT:
base compilers (for C++11 feature support) are gcc 4.8, clang-3.4 (used in OSX build CI)
tested to run with nupic (python)
TODO:
4/ workaround coveralls gcc 4.6 vs 4.8 issue
5/ fix c++11 problems with stdc++ on OSX
Fixes #178.