Re:Java 10 and beyond – a look at the potential language change
by stochastic_monk on Sunday May 13, 2018 @06:14PM
(#17061313)
That's part of why it's such a nightmare to parse.
The GCC C++ parser is over a megabyte of ASCII text. Think about it: it takes over a million characters to figure out how to parse C++ code. This complexity is partially because there are so many ways to do the same thing.
All auto parameters, or make it a template? `if constexpr` or `std::enable_if_t`? Macros for generic programming or variadic variadic template templates? Overloading or specialization?
I love C++, and backwards compatibility is something that's been valuable for it, but it certainly comes with its challenges.
The GCC C++ parser is over a megabyte of ASCII text. Think about it: it takes over a million characters to figure out how to parse C++ code. This complexity is partially because there are so many ways to do the same thing.
All auto parameters, or make it a template? `if constexpr` or `std::enable_if_t`? Macros for generic programming or variadic variadic template templates? Overloading or specialization?
I love C++, and backwards compatibility is something that's been valuable for it, but it certainly comes with its challenges.