On 28-6-2014 4:06, Jon A. Cruz wrote:
On Fri, Jun 27, 2014, at 03:48 PM, Johan Engelen wrote:
You mean to #ifdef the hell out of it? I am very much against this. We already have this in our code, and it is terrible. For me "using C++11" means we require it, full stop.
Well... some is more using typedef, rather than #ifdef. A bit of #ifdef does come in... but "the hell out of it" is probably to the degree we want to avoid.
We are still going to need at least some judicious #ifdef to keep cross-platform and cross-OS support working. However we do want to keep it to a minimum. Explicitly defining what is "too old" will help both users and devs.
It's just that many of the C++11 things we would want to use (and are safe to) are not typedef'able. I'm thinking about: auto, initializer lists, =delete, move, ranged for, enum class, lambda, constructor delegation, ...
The only thing I know of that we probably cannot use yet (or need to do tests with) is the threading functionality.
cheers, Johan