Hi Factor List, A while ago Nat Pryce built a system in python called 'protest' that allowed you to document things with named unittests. I wrote about it here:
http://www.phildawes.net/blog/2006/03/17/protest-rocks-generate-documentation-from-tests/ When I started using scheme I found that it was easy to write a DSL which wrapped the documentation with the unittests for extraction http://www.phildawes.net/blog/2007/05/23/a-simple-scheme-unittest-dsl/ This had a nice reinforcement loop in that documenting the api encouraged you to test it and vice versa. The tests then show up in the documentation to illustrate how the api works. Is there a good reason the same approach wouldn't work well in factor? Cheers, Phil ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
