Imran Rafique scripsit: > Probably the best thing would be to improve individual egg > documentation.
+1 > Once the basic API for an egg has been documented, the thing I look > for most are example code snippets, rather than verbose descriptions > of how to use it. Still a pain in the neck for the egg author to do, > but perhaps slightly easier than writing paragraphs of text? I wonder > if most other "users" thought the same (poll?) I generally seem to want to use an egg in a non-standard way, so I like the documentation. In addition, it's very important to have an introduction explaining what an egg is *for*. Documentation often focuses too much on the what and not enough on the why. Fortunately, documentation is in the wiki, so anyone can fix it. -- Some people open all the Windows; John Cowan wise wives welcome the spring co...@ccil.org by moving the Unix. http://www.ccil.org/~cowan --ad for Unix Book Units (U.K.) (see http://cm.bell-labs.com/cm/cs/who/dmr/unix3image.gif) _______________________________________________ Chicken-hackers mailing list Chicken-hackers@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-hackers
