> changing > > typedef time_t int32_t > > to > > typedef time_t int64_t > > does not change your api Not sure I agree, because time_t itself is part of the

> changing > > typedef time_t int32_t > > to > > typedef time_t int64_t > > does not change your api Not sure I agree, because time_t itself is part of the API, and programs can use it for more than just calling your syscall, like in their own structures. Linux has found they don't need these flag days, they're an ugly old sledgehammer that used to be quite common in systems programming, but Linux (and presumably Windows though I haven't seen the source code to make a judgement) really pioneered much more disciplined, thoughtful, and structured way to manage API and ABIs such that new versions can be brought in with little disruption and old versions can also be maintained usually with little burden to the code base. It's a better system all around IMO, even if you did decide to remove the old stuff right afterwards, the change process is just the right way to go. And keeping around the old stuff and not having to change the world or break your users is actually a good thing too, the ability to make changes less painful than these big hammer flag days makes things very flexible and adaptable.