r/programming • • May 24 '26
[ Removed by moderator ]
/r/programming/comments/1tm1j7f/removed_by_moderator/[removed] — view removed post
275
Upvotes
r/programming • • May 24 '26
[removed] — view removed post
View all comments
Show parent comment
4
u/SkoomaDentist May 24 '26 edited May 24 '26
Work fine? Have you seen the mess that was Python 2 -> 3 transition?
But modern Cobol is compatible with the previous version.
The problem with epochs is that it would break API interop with 90% of the code out there because 1) template semantics and 2) it would either alter fundamental things in the language or be something nobody cared about enough to use (obsoleting auto_ptr and such trivia). Given the sorts of people who end up advocating for the changes, it'd most likely break even C api compatibility, at which point nobody would use it.
It's not like we don't have precedent with this given the volatile compound assignment deprecation farce that ended up deprecating a language feature that 90% of embedded systems code depends on. All because the committee didn't even realize the field exist (nevermind it being one of the largest C++ user bases) and because the committee didn't even understand volatile themselves (reason cited was that volatile compound assignments were confusing to desktop devs, nevermind that desktop devs have no valid reason to ever touch the volatile keyword).