And it never really worked very well, if I recall.

Um, I've seen quite a few reports of bits of evidence that together strongly suggest that the election was rigged. For example, try this: BBC News: Where did all the votes come from?

If the overwhelming majority of Iranians (like the overwhelming majority of Poles) truly support democracy, human rights, and peace with Israel, then a liberal Western democracy will arise -- without any violence.

So that brutal violence in the protests following the election was what exactly?

Using this case as an example: If you use an integer variable for your tick, it's never rounded. Whenever you use it to calculate a time, then you can multiply it by 0.1 to get a much more accurate number than one obtained with the cumulative error of adding on a rounded floating point 0.1 to a rounded floating point sum every tick.

A straight line is just a special case of curve.

... And then you *learn* and don't puke up the next time. Allowing users to lock modes would mean that a lot of people would never find out what's interesting and new about the system. You might end up with a horrible mess once, but then you can look at what you did wrong.

This is why we have terms like 'space opera' - for stories that aren't *about* the science. You could just as easily set the base frame for stories like Star Wars and Babylon 5 anywhere, but they just happen to be in a setting where space travel and building in space is manageable tech. These stories are much more about people and what they do than about the consequences of technological advance or societal change over time.

And perhaps more importantly, is the entire effect countered by wearing tinted glasses?

Sometimes working here feels like banging rocks together. I'm a knapper.

Any derivative does also have to be GPL-ed, though, doesn't it?

But other threads can do processing on the CPU while that's taking place.

<quote>Anybody who tries to change this, should be shown the door. </quote>

Will, but possibly not should.

<quote>You "C" beanies will need C/OPENMPI/OPENMP/TAU to just even try to match Fortran2008's power. Intel knows this, this is why all their parallel libraries, codes and tools are geared for Fortran and NOT C. Live with it...</quote>

Last time I looked, MKL and the Intel compiler were much more focused towards C. Maybe you're thinking of IBM?

As far as I'm aware, those larger systems are ccNUMA -- cache-coherent non-uniform memory access, in which processors have local memory, but can also access other processors' memory via a network layer. It doesn't quite support the same kind of scaling as proper, uniform access shared memory.

And you have to love a language where you can in all seriousness say "And now we must initiate... The Ravenscar Profile."

Not to sound like a fanboy, but <3 OpenMP.

(Though it's not exactly using pthreads directly, even though the majority of implementations are built on pthreads.)