|
I need to know how things are meant to interact with each other, not just a list of methods and properties.
Win32 API documentation is 10 times better, and the old Win16 documentation is priceless - I had to use it to locate a possible bug in the linker (turns out it was a simple mismatch of structure size between exe and DLL but since it was all in the allotted memory space no Access Violation happened, just a static variable misteriously reset to 0 on 'random' occurrences).
GCS d--(d-) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
When I was writing documentation for a complex product with a built-in language (Rexx) and extended functions I ended up writing two documents. A technical Reference that listed everything you could do, lists of API calls, etc. and a User's Guide showing how to do certain tasks and what to use to do them with examples of common things.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|