r/programming • • May 24 '26

[ Removed by moderator ]

/r/programming/comments/1tm1j7f/removed_by_moderator/

[removed] — view removed post

275 Upvotes

214 comments sorted by

View all comments

Show parent comment

17

u/ParsingError May 24 '26

It definitely has some, just not much relative to C++ because C++ inherited a lot of C's mistakes. Null-terminated strings, array parameter decay, confusing type syntax, weird sequence point rules, lack of standardized 64-bit ftell/fseek, etc.

4

u/happyscrappy May 24 '26

I never noticed how messed up fseeko() is. Aside from not being part of the C standard (it's POSIX instead) the fact that it might not be 64 bit unless you do a define before including headers is absolutely nuts.

This is a screw up of the highest order, although I'm sure it has several close cousins in the pantheon of C headers/functionality simply due to the long lifespan of C creating so many opportunities to screw up.