Originally posted by oiaohm
View Post
I see it is using inline functions that call _ctime64 and _difftime64. While I don't know what the function does, 64 in its name is kinda self-explanatory here, dummy.
So yeah, you're definitely not a programmer, can't even read the code that you linked.
Originally posted by oiaohm
View Post
Again, unless you explicitly ask for 32-bit time functions, in this case, you can do whatever you want. Even 16-bit times if that's your thing.
I know it's a shock to you that you can add new functions and exports to an existing library. msvcrt didn't change its 32-bit time functions, it just added 64-bit ones, and libraries like the one you linked transparently map to those with inline functions. Both functions exist at the same time, and all is good, ABI is preserved.
It's a shock to morons like you since it's a thing that seems impossible in Linux userland; instead of adding new APIs, just replaces the original ones, breaking the ABI, because fashionistas must delete "old cruft". That's why it's pathetic.
The kernel also does the same thing: it adds new syscalls, and keeps the old. Forever. Which is why the Linux kernel has a stable ABI.
Leave a comment: