Messages in this thread | | | Date | Tue, 10 Jun 2003 11:41:00 -0700 (PDT) | From | Davide Libenzi <> | Subject | Re: Coding standards. (Was: Re: [PATCH] [2.5] Non-blocking write can block) |
| |
On Tue, 10 Jun 2003, Jesse Pollard wrote:
> On Monday 09 June 2003 13:58, Davide Libenzi wrote: > [snip] > > > > If you try to define a bad/horrible "whatever" in an *absolute* way you > > need either the *absolutely* unanimous consent or you need to prove it > > using a logical combination of already proven absolute concepts. Since you > > missing both of these requirements you cannot say that something is > > bad/wrong in an absolute way. You can say though that something is > > wrong/bad when dropped inside a given context, and a coding standard might > > work as an example. If you try to approach a developer by saying that he > > has to use ABC coding standard because it is better that his XYZ coding > > standard you're just wrong and you'll have hard time to have him to > > understand why he has to use the suggested standard when coding inside the > > project JKL. The coding standard gives you the *rule* to define something > > wrong when seen inside a given context, since your personal judgement does > > not really matter here. > > The coding standards were written by people who said > > "Do it this way because 'I' have to read it and understand it to be able to > maintain it."
The whole sub-thread wasn't talking about democracy in coding styles ;)
- Davide
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |