Another expense might be making the GRAIL orbiters dual-string (duplicate almost everything on a single orbiter, two main computers, two batteries, etc). According to http://moon.mit.edu/spacecraft.html GRAIL is single-string because that matches the mission reliability requirements.
Also - I was on the GRAIL development team and I'm currently working GRAIL mission operations, so I'd also be employed for a little while longer if we repeated this experiment at Mars.
As OP explicitly said C++, I have to wonder, are they looking for an Object Oriented type of framework? If so, GLUT doesn't fit the bill, it's a pure C, function callback oriented framework. It could be used in an OO like manner, but it isn't OO itself.
The only OO framework I've found for use with OpenGL is FLTK, but my experience with OpenGL is quite limited. What other OO frameworks are available and worth the effort to learn?
If you can get to an ER in less time then the Ambulance would take to arrive you are ahead of the game anyhow.
Definitely not true. A stroke victim that goes to the wrong hospital (handling a stroke requires a special set of equipment and skills that not every hospital has) will have to wait for EMS to transport them to the right hospital. Now they've got the time it takes to transport them to the wrong hospital as well as the time it takes to transport them again to the right hospital working against them.
That's typically true no matter where you live. Emergency response times suck universally.
Citation? I've been in a couple automobile accidents and EMS was present within a few minutes. All depends on where you live.
If you can safely move the person you call 911 and start driving. The ambulance can meat you halfway if things are that bad.
Interesting, don't know if it's done or how EMS responds to this.
Yes, I know how expensive an ambulance ride is. It's all absurdly priced, but I guess you avoid the whole billing issue if you die before you even get there. This approach does come with its own set of drawbacks...
It's all a calculated risk, one way or the other. Most people don't understand all of the reasons for taking the ambulance, and so make this decision without all of the info.
Fair enough. Perhaps I should have said call 911 instead of an ambulance. Still might not address your point, and unfortunately I don't know the answer to your question...
This is definitely something to consider if you have the choice on where to live (I recognize that a number of people don't have that choice). I still picked a rural area.
That's what "Medical Charts" are for. Used to be every patient had a chart on a clipboard at the end of the bed.
Until the hospital is fined/sued for violating the patient's rights under HIPPA by leaving their medical records our for all to see...
I'll readily admit that storing the records in a computer isn't much safer, but it's less visible to most people.
I could be wrong, (and I don't know much about mailman) but...
The lock being left behind is generally a file that mailman has created in the file system. Once the file is created, the kernel has no business deleting it. It should close the file and reclaim the file handle when mailman closes, but it shouldn't delete the file. Ideally, mailman would create the file in a section of the file system that is cleared on reboot (/tmp?), so this wouldn't be a problem...
Add to that the fact that most "modern" IDE's will automatically suggest member functions for an object and nobody even has to look at the API or any other type of documentation to really screw things up anymore!
The sad part is that I know I'm guilty of doing exactly this.
At least now I'm protected from myself; if vi has that capability I don't know how to use it...
No amount of careful planning will ever replace dumb luck.