Re:C++ Pattern Matching Proposal [pdf]
by Supermancho on Friday January 03, 2020 @08:28PM
(#21952111)
> You can only create a new, almost identical language,
Thats demonstrably false. Python was a loud transition, but most of the language warts and syntax is still there. Same as the Php and perl transitions and the wacky es6 or java. The list goes on.
Re:C++ Pattern Matching Proposal [pdf]
by a1369209993 on Friday January 03, 2020 @09:32PM
(#21952405)
> most of the language warts and syntax is still there.
> > new, almost identical language,
Emphasis added.
Re:C++ Pattern Matching Proposal [pdf]
by Supermancho on Saturday January 04, 2020 @07:09PM
(#21958621)
>> new, almost identical language,
Either it means it's a different language or it's a new language. The ambiguity in interpretation leads to a statement of non-meaningful change (tautology) or a statement of important change. The gracious interpretation is the only thing worth responding to, not quibbling over the possible non-statement.
Re:C++ Pattern Matching Proposal [pdf]
by a1369209993 on Friday January 03, 2020 @09:30PM
(#21952399)
> This is what happened to Python2/3.
Nitpick (and also proving your point): there is no language Python2; you mean Python vs Python3.
Languages are effectively immutable. Unless you can reach out and edit every single piece of code that breaks when you remove a feature, you can't remove a feature from a language. You can only create a new, almost identical language, and then spend a decade migrating people. This is what happened to Python2/3.
Very few things have been successfully deprecated in C or C++. Even massive security holes in the standard library.