3 ms·
We tended to use libraries or external dependencies, too. (And when that was out of the question, C++11 and later usually were as well)
by gcp 10y ago
We tended to use libraries or external dependencies, too.
(And when that was out of the question, C++11 and later usually were as well)
- stcredzero 10y agoYou should be able to build facades around that stuff, so your main codebase is all C++11.
- pjmlp 10y agoThat doesn't scale in big code bases, or in the typical corporate culture.
- stcredzero 10y agoI know for a fact this isn't necessarily true.
- pjmlp 10y agoI don't mean it never works, just that is it seldom the case. I know C++ since the C++ARM days, it is one of the languages I like most despite its warts, teached it to first year students before C++98 happened. Nowadays I spend my work hours in Java and .NET stacks, but still do occasionally use it, when needed. I never worked in a company, with exception of my time at CERN, that actually followed C++ best practices. So yeah, there are lots of companies making good use of C++, as proven by CppCon and C++Now talks, but they seem to be the minority, when you take into consideration the ones whose main business is not selling software. At least I was pleased to see the BMW presentations at FOSDEM, where they mentioned moving from C to C++14, as a means to improve safety on car systems.
- stcredzero 10y agoSo yeah, there are lots of companies making good use of C++, as proven by CppCon and C++Now talks, but they seem to be the minority, when you take into consideration the ones whose main business is not selling software. I should be more thankful about my current job, then. I guess a good heuristic for judging a language is to go to conferences and see what is portrayed there, then "dividing by 8." That will get you to about the level of the average shop.
- gcp 10y agoThis doesn't even address the problem at all: you still have to deal with the non-C++11 code to write the facade (and fix bugs in the underlying code).