>> Unfortunately, most people don't seem to realize that a *library* with 
>> no documentation is worse than useless.
> 
> Good libraries should be intuitive and self-evident enough.  Bad 
> libraries shouldn't be used anyway.

Nice in theory, not always possible in practise. Sometimes it's 
unavoidable that when a library offers a lot of functionallity, it's not 
obvious how to start using it - even if it *is* easy to use once you 
know how.

This is why documentation is necessary.

(Also, I don't care how intuitive a library is, there are usually 
edge-cases where it's not obvious what the library will do. Usually you 
need to know about these.)

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message