purple
> > >> I might like to signal Devel::Cover that func() has a constant return (or > >> lack thereof). > > > > > > however, in the process of development we are required to analyze any of the > inevitable gaps and decide whether the unhit condition is valid. if it is > we write a test for it. if it represents a condition we would explain away > (D::C limitation, or whatnot) then it would be nice to have some way to > track it within the tool itself. partially to appease management with heavy > greens, but more to save development cycles chasing down issues I (or other > developers) have analyzed before. D:C might need another color which is displayed in such cases. Once I got a red, analyzed the situation and decided it is a good red I'd like to be able to signal Devel::Cover about it. Still I'd like to be able to easily see which cases were "missed, but OK". It could be reported somehow with a color such as dark green or purple. This extra color still leaves place for questions on the side of the management so there could be a flag such as --mcl (manager compatible report) that would turn all the purple parts to be green. Gabor
