Comments on: Doctest for Ruby http://blog.ianbicking.org/2007/08/23/doctest-for-ruby/ Wed, 08 Sep 2010 10:58:09 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: sebn http://blog.ianbicking.org/2007/08/23/doctest-for-ruby/comment-page-1/#comment-151517 sebn Wed, 10 Feb 2010 19:40:50 +0000 http://blog.ianbicking.org/2007/08/23/doctest-for-ruby/#comment-151517 Bryan: ok, I probably missed something, thanks for the comment. Bryan: ok, I probably missed something, thanks for the comment.

]]> By: Bryan Larsen http://blog.ianbicking.org/2007/08/23/doctest-for-ruby/comment-page-1/#comment-149349 Bryan Larsen Fri, 29 Jan 2010 19:02:16 +0000 http://blog.ianbicking.org/2007/08/23/doctest-for-ruby/#comment-149349 sebn: we use rubydoctest for most of the documentation for the Hobo project: http://cookbook.hobocentral.net/manual/toc. We never use the doctest: directive, never give test names, never use doctest_require and always hide our boilerplate and setup. sebn: we use rubydoctest for most of the documentation for the Hobo project: http://cookbook.hobocentral.net/manual/toc. We never use the doctest: directive, never give test names, never use doctest_require and always hide our boilerplate and setup.

]]> By: sebn http://blog.ianbicking.org/2007/08/23/doctest-for-ruby/comment-page-1/#comment-133459 sebn Thu, 15 Oct 2009 07:28:22 +0000 http://blog.ianbicking.org/2007/08/23/doctest-for-ruby/#comment-133459 "it doesn’t let you hide any boilerplate and setup" The ruby implementation sucks, IMHO, since: - it force me to put a "doctest:" directive before every example - it force me to give a "test name" to my examples (hey, I'm writing a documentation, not a testcase!) - "it [effectively] doesn’t let you hide any boilerplate and setup", which sucks for rails, since I'll not use my code outside of this setup, and since it requires me to put some "doctest_require" directive before my examples (whereas in python doctests, I can accomplish some setup during the DocTestSuite instanciation). - as a result, it doesn't feel natural, and sucks as a documentation “it doesn’t let you hide any boilerplate and setup”

The ruby implementation sucks, IMHO, since: - it force me to put a “doctest:” directive before every example - it force me to give a “test name” to my examples (hey, I’m writing a documentation, not a testcase!) - “it [effectively] doesn’t let you hide any boilerplate and setup”, which sucks for rails, since I’ll not use my code outside of this setup, and since it requires me to put some “doctest_require” directive before my examples (whereas in python doctests, I can accomplish some setup during the DocTestSuite instanciation). - as a result, it doesn’t feel natural, and sucks as a documentation

]]> By: roger http://blog.ianbicking.org/2007/08/23/doctest-for-ruby/comment-page-1/#comment-16473 roger Wed, 02 Apr 2008 14:57:42 +0000 http://blog.ianbicking.org/2007/08/23/doctest-for-ruby/#comment-16473 Yea! one less lib for me to write :) Yea! one less lib for me to write :)

]]> By: Paddy3118 http://blog.ianbicking.org/2007/08/23/doctest-for-ruby/comment-page-1/#comment-331 Paddy3118 Fri, 24 Aug 2007 05:42:15 +0000 http://blog.ianbicking.org/2007/08/23/doctest-for-ruby/#comment-331 Its great to see the idea of doctest spreading - every Dynamic language with a shell interface should have it! Maybe someone should prompt those Perl 6 guys :-) Thinking about these new versions made me add to the doctest wikipedia page a comment about <b>not</b> mentioning on the wiki page until they became language standards though. This in turn gave me a great way of tidying-up the wikipedia Duck Typing entry so thanks. - Paddy. Its great to see the idea of doctest spreading – every Dynamic language with a shell interface should have it!

Maybe someone should prompt those Perl 6 guys :-)

Thinking about these new versions made me add to the doctest wikipedia page a comment about not mentioning on the wiki page until they became language standards though. This in turn gave me a great way of tidying-up the wikipedia Duck Typing entry so thanks.

  • Paddy.
]]>