Then hopefully we'll be able to get limited evaluation at compile time some time in the future, as they define what limited is. Hopefully.
This is a discussion on reliably checking for overflow before addition? within the C++ Programming forums, part of the General Programming Boards category; Then hopefully we'll be able to get limited evaluation at compile time some time in the future, as they define ...
Yes, this is very significant also. Remember, you can never back something out of a standard, only add to it, if you want to keep backward compatibility.Easier in the first instance (particularly with a large language like C++) to specify something in a restricted manner, and only relax restrictions if there is a real world need to do so.
The only exception I know of is the auto keyword, whose old meaning will be removed completely. That's safe because absolutely nobody used that keyword, and even if someone did, it's completely redundant anyway.
All the buzzt!
"There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
- Flon's Law