3 ms·
After reading the C++ FAQ on this I can accept that using tyepdef may have been impossible/confusing, but why overload "using"? This is one of the things that
by AlexandrB 14y ago
After reading the C++ FAQ on this I can accept that using tyepdef may have been impossible/confusing, but why overload "using"?
This is one of the things that makes C++ mega-complicated. The same keywords have different meanings based on context, when really a new keyword should just have been used. For example "virtual" functions vs "virtual" inheritance.
- skrebbel 14y agoThe moment you add a keyword to a popular language, you break lots of existing code that happen to have that keyword as an identifier, e.g. as a variable, class or function. This means that when adding features that need a new keyword, you best overload an existing one. It's for this reason, too, that Java 7 overloaded `try` to implement some sort of poor-man's-RAII-support, instead of adding a new keyword (such as C#'s `using`, which does the same, and was by the way also overloaded for the same reason)