In particular, interfaces between two languages that are not C are often difficult to construct
(Yes, I know what they mean. I think they meant to write "In particular, interfaces between two languages (when neither is C) are often difficult to construct".
Still, it amuses me to think about making an interface from C... to C
"Although carbon nanotube based processors are showing promise [...]."
Go, speed-editor, go!
If anyone's interested, we could probably find some open source software to run a betting pool on how
He started his explanation by saying that a good exam would have:
* several of no-brainer questions to check if everyone had at least done the minimum and give them a warm-up for the real questions
* several of real questions, to make sure people actually did study, and to produce some differentiation amongst the general population
* one or two incredibly difficult questions. Questions so tough that most people are NOT expected to get them. Questions so tough that if you do get them then you the prof should come talk to you about majoring in the area (the prof taught Freshman/Sophomore level math).
According to him the point of grading on a curve was to be able to put that third category of questions on the exam without destroying the grade of everyone else in the room.
I, personally don't grade on a curve but I thought it was interesting that it can serve a purpose in some situations.
"instead I got an unicorn"?
A unicorn sounds right to me, your rule seems right to me, but I can't quite reconcile them. Ah, cognitive dissonance
-Wait, you mean the other Java, don't you.
Yeah, ok, that makes more sense.
But thank you for posting a summary that's nearly 50% questions!