NFD

How do we want to proceed here?

My suggestion is:

• For all applications (NFD, ndn-tools, NLSR if the maintainers are interested, etc..) we use whatever C++ dialect is the default for the current compiler (except that we use -std=c++NN instead of -std=gnu++NN), with a minimum of -std=c++11 if the default is pre-C++11.

• For ndn-cxx we can do the same as above, or we can always force -std=c++11 even if the compiler is more capable. I don't expect any ABI incompatibilities between C++11 and C++14, so we should be safe either way.

In any case, we cannot use any C++14 features in the code (unless a fallback is provided) because we still have to support gcc-4.6.

I don't think the benefit-cost ratio is favorable for enabling C++14 now.

Per platform policy, Ubuntu 12.04 compatibility will be dropped after Ubuntu 16.04 release, which is about 2 months away.

We can consider enabling C++14 at that time.

Sure, I'm not in a rush to implement this. Just wanted to start the discussion.

Note that even gcc-4.8 contains very few C++14 features, so we still wouldn't be able to use it if we dropped support for earlier compilers. But we'd gain complete C++11 support, which would be pretty nice.

I haven't worked on this and doubt would have time anytime soon. Eric can try to instantiate 16.10 vagrant slaves https://github.com/cawka/ndn-jenkins-slaves in another environment and try to debug, if there is enough capacity available.

I actually built ndn-cxx and NFD with C++14 (-std=c++14) using GCC 6 on Ubuntu 16.10 back in January and didn't encounter any compilation issues. I didn't test them, however.

Missing: IntegrationTests install_helpers/tools/Makefile

Missing: patch for ndns. It works before but does not work after.
Missing: pull request for ndnmapDataCollector, to avoid problems upon next release.
Other patches are good.