-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Donnie Berkholz wrote: > > Yes, you have a good point, as it applies to ebuilds. But there are still > potential incompatibilities in the source itself that this cannot solve. > At least for the ebuild side, perhaps we should get some sort of automated > tool that can analyze all possible code paths and spit out a list. >
Does anybody outside of aerospace contractors do this? For even a fairly rudimentary piece of software the number of paths to test would be insane. There is a reason that even modern spacecraft have UIs that consist of operators typing obscure codes into keypads which operate single-threaded control systems. It is about the only way to make it possible to test the software thoroughly. Toss in multitasking and and good luck with code-path analysis... Sure, automated test suites are great, but even packages with tons of automated tests still have bugs. At some point you hit the point of diminishing returns and you have to ask yourself just how perfect the software really needs to be... -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGvbXNG4/rWKZmVWkRAn77AJwL76AsBqO1ZZDlyKrZMvczPqTbQwCgm7Cs hOEAs4cI4H9Y1abgtuIe4lE= =l/5D -----END PGP SIGNATURE-----
smime.p7s
Description: S/MIME Cryptographic Signature
