In article <[EMAIL PROTECTED]>, Nathan S. Haigh <[EMAIL PROTECTED]> wrote:
> A suggestion was to have different levels of > "strictness" in Test::Kwalitee and have different sets of metrics being > tested by > default at each of those levels. However, I didn´t get into this and simply > hard-coded some of the metrics to be skipped. I think that's a bit out of Test::Kwalitee's scope. It basically wraps each of the metric code refs in the testing framework and provides access to those things individually. It's then up to the user to decide which functions he wants to use. I'd leave Test::Kwalitee just like it is, feature-wise, and not have it dictate use or practice. Let it just provide the ability. Sub-classes and user classes, which probably have a much better chance of being maintained, should be the way to go. That's just my two cents though, and I'm willing to help clear out the current issues no matter which way it goes.
