3 ms·
There's a chicken and egg problem with formal methods, which is that they're really hard, so nobody does them. But part of the reason they're really hard is tha
by jerf 16y ago
There's a chicken and egg problem with formal methods, which is that they're really hard, so nobody does them. But part of the reason they're really hard is that nobody does them, so not much time has been spent optimizing the process of generating them, and when you sit down to write a proof you don't have large libraries of already-proved code to draw from. Does your XML parser carry any proofs? Heck no.
A few people seem to be doing research on this problem, like the authors of Coq, but until the chicken/egg problem is solved I'm not optimistic about it even penetrating the obscure language community, let alone the mainstream. Plus nobody is really sure just how far we can go in making it easier, if we were able to share libraries and common practices; it will always be a challenge, certainly, just as writing good code is today anyhow, but can it ever exceed breakeven in terms of costs/benefits for a significant fraction of the code in the world? I'm cautiously pessimistic, but would love to be proved wrong.