[boost] Re: [1.33.0] Feature freeze tonight

From: Aleksey Gurtovoy (agurtovoy_at_[hidden])
Date: 2005-04-23 03:12:16

Doug Gregor writes:
> On Apr 22, 2005, at 10:58 AM, Peter Dimov wrote:
>
>> Doug Gregor wrote:
>>> Would making the color of expected failures something that's not green
>>> (everything's okay) and not yellow or red (something's broken) work
>>> for you? That would be useful for me, because I'm noticing that for
>>> certain compilers the number of expected failures in the Graph lib is
>>> approaching the number of tests... but that's not obvious at first
>>> glance.
>>
>> Yes, this would be good enough. I wasn't sure whether this would be
>> OK with everyone else; there's probably a reason for making expected
>> failures and passes the same color.
>
> I can't think of any compelling reason to have them the same color,
> though I guess the "all-green" detailed summary could give one warm
> fuzzies that you wouldn't get with grey expected failures... 

The "warm fuzzies" were actually the original reason for their current
coloring :).

> but I'd much rather have grey expected failures so users can know
> what works and what doesn't at a glance.

Note that eventually (soon, I hope) we will have a "User View"
specifically tailored to user needs.  This aside, grey has grown on me
as well.

-- 
Aleksey Gurtovoy
MetaCommunications Engineering