3 ms·
I don't think the author has read the Ariane crash report, which says: > Although the source of the Operand Error has been identified, this in itself did not c
by dalke 12y ago
I don't think the author has read the Ariane crash report, which says:
> Although the source of the Operand Error has been identified, this in itself did not cause the mission to fail. The specification of the exception-handling mechanism also contributed to the failure. In the event of any kind of exception, the system specification stated that: the failure should be indicated on the databus, the failure context should be stored in an EEPROM memory (which was recovered and read out for Ariane 501), and finally, the SRI processor should be shut down.
> It was the decision to cease the processor operation which finally proved fatal. Restart is not feasible since attitude is too difficult to re-calculate after a processor shutdown; therefore the Inertial Reference System becomes useless. The reason behind this drastic action lies in the culture within the Ariane programme of only addressing random hardware failures. From this point of view exception - or error - handling mechanisms are designed for a random hardware failure which can quite rationally be handled by a backup system.
> ... An underlying theme in the development of Ariane 5 is the bias towards the mitigation of random failure. The supplier of the SRI was only following the specification given to it, which stipulated that in the event of any detected exception the processor was to be stopped. The exception which occurred was not due to random failure but a design error. The exception was detected, but inappropriately handled because the view had been taken that software should be considered correct until it is shown to be at fault. The Board has reason to believe that this view is also accepted in other areas of Ariane 5 software design. The Board is in favour of the opposite view, that software should be assumed to be faulty until applying the currently accepted best practice methods can demonstrate that it is correct.
There were also questions about why the code was even still in operation. The functionality was useful under Ariane 4 but not Ariane 5, the code "serves no purpose" after launch, analysis was done to check some variables for overflow but not all variables, and the component's functional requirements weren't updated to reflect the new launch trajectory data.
To say it's only because of an exception during type conversion ignores the whole, very important context, which says that the exception wasn't the real problem.
- mpweiher 12y agoYes, the author did read the report, did the esteemed critic? "It was the decision to cease the processor operation which finally proved fatal." Which is exactly what the author argues against: don't terminate the process on integer overflow.
- zvrba 12y agoDon't terminate a mission-critical process. Garden variety software: yes, PLEASE, DO kill it. You don't seem to realize that many of SW practices that are adequate for "normal" software, are NOT applicable to mission-critical, fault-tolerant scenarios.
- mpweiher 12y agoWhat's mission critical depends on the mission, it's not the language's job to decide what is or is not mission critical. Please tell me why killing my spreadsheet program is OK because the cat walked on the keyboard.
- pohl 12y agoIf it's the case that your spreadsheet program can tolerate overflow on addition, shouldn't that program be using the &+ operator instead of the + operator? If, instead, detecting and responding to the overflow is what you want, then someone has already filed a rdar on that and Chris Lattner has replied saying: "It would be straight-forward for us to provide arithmetic functions that return the result as an optional (i.e., nil on overflow). We'll take a look, thanks for filing a bug!" https://devforums.apple.com/thread/232791 https://devforums.apple.com/thread/232791
- mpweiher 12y agoSorry, I'd rather have a language with sensible defaults. In this case, the sensible solution would be to have a proper Numeric tower like, for example, Smalltalk, where such overflows simply don't matter. The default "Int" type should be part of that system. You can then add Int32/Int64 or maybe IntNative to get to the built-in processor types, which then have built-in processor behavior, and possibly arithmetic overflow traps as an extension. The current defaults are just nuts, IMHO.
- pohl 12y agoYou've made that pretty clear in your writings (which I have enjoyed, by the way.) I'm curious, do you want Swift to be that language - and, if so, have you been participating in the dev forums[1] and filing bug reports into rdar? Would you mind sharing the rdar number that you filed about this issue so that others whose preferences lean in the same direction can add our voices to the chorus? And, if not, what is your goal? Edit: I see that you've answered my question on your blog[2] by answering someone else who asked the same thing. Thank you! [1] https://devforums.apple.com/community/tools/languages/swift https://devforums.apple.com/community/tools/languages/swift [2] http://openradar.appspot.com/17472835 http://openradar.appspot.com/17472835