6 ms·
Even if it's valid behavior, it's still a breaking change. The function never set this error code before, now it does, and at least 3 large projects are not wor
by foepys 6y ago
Even if it's valid behavior, it's still a breaking change. The function never set this error code before, now it does, and at least 3 large projects are not working anymore.
- matwood 6y agoCould Apple be better at communicating changes like this? Absolutely. Is Apple in the wrong here? No. This is a documented return code that has been ignored. What's the point of a standard if they can't use it?
- SubjectToChange 6y agoApple isn't following POSIX by ignoring SA_RESTART. What is the point indeed.
- bobbylarrybobby 6y agoI don’t think violating Hyrum’s law should be considered a breaking change, but I suppose that that’s a matter of opinion.
- SubjectToChange 6y agoHyrum's law doesn't apply here. Tons of software is liable to be broken by this and at least three big projects have been broken by it. Furthermore, Apple isn't even obeying POSIX since it is ignoring SA_RESTART. It's a breaking change.