I stand corrected. It looks like Polyspace came mostly from academia.
It's also interesting that it was associated with the launch of a European rocket, Ariane 5. Everyone knows that the space race in the 1960s helped to push technology ahead in the United States; I guess that still happens, at least to a certain extent.
I think this kind of research is really interesting. It seems like it could help create more efficient compilers and perhaps better tools.
For what it's worth, I like static type systems. I really hope that in the future, we'll be able to have more and more information about programs even before running them. Programmers ought to be free from the drudgery of spotting typos or passing the wrong arguments to functions. Or even accidentally dereferencing a pointer before assigning it. As I said before, though, there are always things in the design that are impossible to "prove" (in the mathematical sense), like user interface, the performance of heuristic algorithms, and artistic design.
What every C Programmer should know about undefined behavior #2/3
Posted May 18, 2011 5:02 UTC (Wed) by price (subscriber, #59790)
[Link]
Huh, nice observation re: this technology being connected to the space race. I hadn't made that connection.
Definitely beats Tang, if you ask me.
What every C Programmer should know about undefined behavior #2/3
Posted May 19, 2011 3:53 UTC (Thu) by raven667 (subscriber, #5198)
[Link]
If Feynman is to be believed then a significant part of modern technological living was developed at least in part as part of the space race and this is evidence that this continues to be true at a smaller scale.
What every C Programmer should know about undefined behavior #2/3
Posted May 19, 2011 13:11 UTC (Thu) by marcH (subscriber, #57642)
[Link]