:) So do you think that Google (or Yahoo, or any other 'free' services - no discrimination here) are doing this because they are kinded heart? Not everything it's payed with money. Think of all infos they gather from their grateful users.
You should be very careful. Almost mothing it's free in the world. Or if you think I'm mistaken, maybe you already sold your soul:D (or brains on the second thought;) )
Slashdot Mirror
:) So do you think that Google (or Yahoo, or any other 'free' services - no discrimination here) are doing this because they are kinded heart? Not everything it's payed with money. Think of all infos they gather from their grateful users.
:D (or brains on the second thought ;) )
You should be very careful. Almost mothing it's free in the world. Or if you think I'm mistaken, maybe you already sold your soul
Martin Fowler has a very comprehensive book on refactoring - Refactoring: Improving the Design of Existing Code (On Amazon)
The Russians are not the only ones with shuttle problems. Unfortunately the list is long:
Ariane 5 (1996) - distruction at 40 seconds after launch. Cause: 64-16 bit conversion generated an uncatched exception in both main and backup module.
Mars Pathfinder (1997) - was frequently reseting. The cause: priority inversion between processes with shared resources.
Mars Climate Orbiter (1998) - desintegration while entering the athmosphere. Cause: errors at conversion between American and European metric system.
As you see, what happened with Soyuz was nothing compared with the rest.
A efective solution can be Formal Verification (.ps article by Joost-Pieter Katoen) - authomatic tehniques for verifying finite state concurent systems as is defined in Clark, Grumberg and Peled's book - Model Checking