On Sat, 2005-04-16 at 20:59 -0500, Andy Lester wrote:
> > I'm about halfway ready to propose 'has_indentation' as a kwalitee
> > metric.
> And the more the better!
Well sure. Two-space indent is clearly better than one-space indent,
and four-space is at least twice as good as that.
It falls do
I'm about halfway ready to propose 'has_indentation' as a kwalitee
metric.
And the more the better!
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
On Sat, 2005-04-16 at 19:31 -0400, Michael Graham wrote:
> I'm not suggesting that end users be forced to *run* your development
> tests. Just that the tests be included in your CPAN package. Ideally,
> the install process can be made smart enough to skip this kind of test.
"Shipping tests but
> Michael Graham wrote:
> > Another good reason to ship all of your development tests with code is
> > that it makes it easer for users to submit patches with tests. Or to
> > fork your code and retain all your development tools and methods.
>
> Perl::MinimumVersion, which doesn't exist yet, coul
Michael Graham wrote:
Another good reason to ship all of your development tests with code is
that it makes it easer for users to submit patches with tests. Or to
fork your code and retain all your development tools and methods.
Perl::MinimumVersion, which doesn't exist yet, could check that the
v
Christopher H. Laco wrote:
Tony Bowden wrote:
On Thu, Apr 07, 2005 at 12:32:31PM -0400, Christopher H. Laco wrote:
CPANTS can't check that for me, as I don't ship those tests.
They're part of my development environment, not part of my release
tree.
That is true. But if you don't ship them, how do
* Decide where to send test output, and where to allow other output to
be sent. Test::Builder clones STDERR and STDOUT for this purpose. We'll
probably have to do it by overriding C, but it'd be
good to allow users to define alternate outputs (tests may not always
run in a browser, eh?). Maybe
David Wheeler wrote:
On Apr 7, 2005, at 11:32 AM, Christopher H. Laco wrote:
OK, now whos gonna build JPANTS? :-)
JSPANTS, you mean? I think we need a CJSPAN, first. Alias?
Yes well... I'm getting there slowly.
JavaScript::Librarian + Algorithm::Dependency + YAML ought to be enough
to get some b
