3 ms·
What’s the alternative to rewriting? Just recompiling? Assuming the code on the receiving end stores the value in 32 bits (and not a time _t which can magicall
by alkonaut 5y ago
What’s the alternative to rewriting? Just recompiling?
Assuming the code on the receiving end stores the value in 32 bits (and not a time _t which can magically change meaning but a 32 bit integer) then it’s still doomed without rewrite?
I mean even with time_t use you can’t just recompile and make it work because there could be subsequent assumptions that the size of a struct containing a time_t will be a specific size or allocations will be too small or misaligned and so on.
- rwaksmunski 5y agoYes, the alternative to rewriting is changing the size and recompiling. OpenBSD somehow managed to pull it off.
- alkonaut 5y agoBut the problem isn't really changing the OS to return a 64bit value where it used to return 32, the problem is all the applications that assumed it would be 32. By "pulling it off" you mean, they changed it and planes didn't crash around them?
- rwaksmunski 5y agoYes, stuff broke in the ports collection. Not sure about planes but at least one monitor exploded.
- alkonaut 5y agoThat still seems like software under the “control” of the OS maintainers. But most apps running on an OS are never seen by the people maintaining the OS. That’s why it’s such a tricky move to break compat with those apps X because you cant know what they are doing and how.