Re: Change 22021: Upgrade to Test::Harness 2.40.

2003-12-31 Thread darren chamberlain
* Jim Cromie [2003/12/31 09:15]: > the diag()s just helped me find the broken tests. Isn't that what test names are for? (darren) -- In order to make an apple pie from scratch, you must first create the universe. -- Carl Sagan pgp0.pgp Description: PGP signature

Re: Change 22021: Upgrade to Test::Harness 2.40.

2003-12-31 Thread Rafael Garcia-Suarez
Jim Cromie wrote: > >ok() goes to stdout by default, diag() to stderr > > > > which is, I presume, why perl -Ilib t/foo.t produces more output than > make test. > I see that as a feature.I guess note() should go to stderr - for my > preferences at least. Then just do *note = \&diag :) > >

Re: Change 22021: Upgrade to Test::Harness 2.40.

2003-12-31 Thread Jim Cromie
Rafael Garcia-Suarez wrote: Jim Cromie wrote: Well, it seems Ive been abusing diag() for some time now :-O Is there a 'right' way to do this ? perhaps just using ok() ? ok() goes to stdout by default, diag() to stderr which is, I presume, why perl -Ilib t/foo.t produces more output tha

Re: Change 22021: Upgrade to Test::Harness 2.40.

2003-12-31 Thread Rafael Garcia-Suarez
Jim Cromie wrote: > > Well, it seems Ive been abusing diag() for some time now :-O > > Is there a 'right' way to do this ? perhaps just using ok() ? ok() goes to stdout by default, diag() to stderr > or maybe a new function, ex: note() is better: > > note.

Re: Change 22021: Upgrade to Test::Harness 2.40.

2003-12-31 Thread Jim Cromie
Andy Lester wrote: wrt RGS feedback, I don't get the rationale for this change; diag() is supposed to be used for error/diagnostic messages, right ? not for comments, more mundane in nature. (This perturbs the nice line-up of my test logs. Go ahead and patch it. I'll add an "unless $ENV{PER