| 1 |
On Fri, Mar 23, 2012 at 12:37 PM, Ciaran McCreesh |
| 2 |
<ciaran.mccreesh@××××××××××.com> wrote: |
| 3 |
> On Fri, 23 Mar 2012 11:17:56 -0700 |
| 4 |
> Alec Warner <antarus@g.o> wrote: |
| 5 |
>> In general if you are going to say 'this usage is wrong' then you need |
| 6 |
>> some kind of tool to detect and report on it; otherwise a subset of |
| 7 |
>> developers will get it wrong. Don't make it easy to do the wrong |
| 8 |
>> thing, make it easy to do the right thing. |
| 9 |
> |
| 10 |
> Unfortunately, bash really doesn't make it easy for us to do that sort |
| 11 |
> of thing... |
| 12 |
|
| 13 |
Its more a dig at the process in general. I don't aim for perfect |
| 14 |
checks (bash is hard, waa waa waa), but arguably we don't even try to |
| 15 |
write checks that are non-perfect. We end up in situations where one |
| 16 |
guy does it the wrong way, then people copy and paste his code and |
| 17 |
suddenly it is done wrong in dozens of places. QA warnings help let |
| 18 |
people know that what they are doing is likely wrong. |
| 19 |
|
| 20 |
-A |
| 21 |
|
| 22 |
> |
| 23 |
> -- |
| 24 |
> Ciaran McCreesh |
Archives