[e-lang] An attack on a mint

[Raoul Duke]

>  > things you want it to do) but not so good when you want to ensure
>  > that undesired behavior is absent (that the code doesn't do bad
>  > things you don't want it ever to do).

Ja, everything is probabilistic when you get right down to it. It is a
question of to what degree, and how do you want to get a handle on the
range of possibilities.

Testing (in various forms) can be a great tool to those ends.
Specifications would be good. Specifications with testing would be
good. Automated tests generated from specs would be good. Etc.

(the QuickCheck paper(s) for Erlang are a great read.)

sincerely.