Re: Satellite-killing software
It's not Friday yet but what the heck . . . I saw a story about that
Japanese satellite that failed in flight, on a site called
hackaday.com.Apparently it malfunctioned after a software update went awry.
I'm offering 5 to 2 they didn't bother to comment the code. Any takers?
I think they commented the code and then wrote more code based upon reading the comments instead of the code. Only certain of the comments in code are good enough to instill caution and perhaps inspire a search for deeper understanding. My favorite one of those is this:
* Switch to stack of the new process and set up
* his segmentation registers.
* If the new process paused because it was
* swapped out, set the stack level to the last call
* to savu(u_ssav). This means that the return
* which is executed immediately after the call to aretu
* actually returns from the last routine which did
* the savu.
* You are not expected to understand this.
rp->p_flag =& ~SSWAP;
* The value returned here has many subtle implications.
* See the newproc comments.
See https://www.bell-labs.com/usr/dmr/www/odd.html for Dennis Ritchie's explanation.
Here's a picture of Dennis with friends: https://commons.wikimedia.org/wiki/File:Usenix84_1.jpg
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com
Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.
Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com
Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives
Satellite-killing software: From: Keith Hood
Search our Technical Writing Archives & Magazine