On Fri, Mar 23, 2012 at 12:37 PM, Ciaran McCreesh
<ciaran.mccreesh@...> wrote:
> On Fri, 23 Mar 2012 11:17:56 -0700
> Alec Warner <antarus@g.o> wrote:
>> In general if you are going to say 'this usage is wrong' then you need
>> some kind of tool to detect and report on it; otherwise a subset of
>> developers will get it wrong. Don't make it easy to do the wrong
>> thing, make it easy to do the right thing.
>
> Unfortunately, bash really doesn't make it easy for us to do that sort
> of thing...

Its more a dig at the process in general. I don't aim for perfect
checks (bash is hard, waa waa waa), but arguably we don't even try to
write checks that are non-perfect. We end up in situations where one
guy does it the wrong way, then people copy and paste his code and
suddenly it is done wrong in dozens of places. QA warnings help let
people know that what they are doing is likely wrong.

-A

>
> --
> Ciaran McCreesh