> The problem is that the documentation may not be correct, > sending your coders on a wild goose chase.
Anything may contain errors. I don't think this is a valid reason for not doing it. > Think of the source code as a safe but boring investment > (with little barrier to entry), and the documentation as one > with high potential yield (with a high barrier to entry) but > significant risk of errors. Reverse engineering from source code is extremely time consuming and prone to errors too. Given the choice I would always prefer documentation to reverse engineering. BTDTGTTS. > Now, go balance your software portfolio for whatever > risk/reward ratio you find optimal. > > Remember, many code for their own benefit, but documentation > benefits others (mostly), so it's hard to encourage high > quality documentation without paying for it. I'd say documentation benefits everyone. How to the developers know what to implement if there is no documentation? What do they test the code against? etc........ Mark. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
