On Thu, Feb 14, 2013 at 4:59 AM, Dave Rolsky <autarch@urth.org> wrote: > On Wed, 13 Feb 2013, Ricardo Signes wrote: > > For example, again: >> >> ~$ head -1 dupes >> use 5.16.0; >> ~$ perl -E 'my $x = "dupes\n"; open my $fh, "<", $x or die "cannot open >> $x: >> $!"' >> cannot open dupes >> : No such file or directory at -e line 1. >> >> Or: >> >> ~$ cat files.txt >> dupes >> ~$ perl -E 'while (<>) { open my $fh, "<", $_ or die "cannot open $_: >> $!"; >> print <$fh>; }' files.txt >> cannot open dupes >> : No such file or directory at -e line 1, <> line 1. >> >> I think at this point I'm going to stop. The whole document needs to be >> checked for accuracy of these kind of claims before it is possible to even >> consider merging. >> >> Committers: do not merge this branch yet. >> > > What this tells me is we really need to start incorporating tests into the > documentation. I did this with the Moose Cookbook documentation and it was > _very_ helpful. > > I guess the question is how to do this without bloating the core even > more. I don't see us putting Test::Inline in core. I'm using Dist::Zilla::Plugin::Test::Synopsis with great success in all my modules, testing doc code is definitely a good thing. > > > -dave > > /*============================**==============================**== > http://VegGuide.org http://blog.urth.org > Your guide to all that's veg House Absolute(ly Pointless) > ==============================**==============================***/ >Thread Previous | Thread Next