| 1 |
On Sat, 2001-11-10 at 23:14, Aron Griffis wrote: |
| 2 |
> Daniel Robbins wrote: [Sat Nov 10 2001, 01:24:42PM EST] |
| 3 |
> > 1) Use one tab per indent |
| 4 |
> > |
| 5 |
> > 2) Put comments on separate lines |
| 6 |
> > |
| 7 |
> > 3) Avoid using "/" line continuation characters and use long lines instead. |
| 8 |
> |
| 9 |
> I don't care about 1 and 2, but I agree with Chouser about long lines. |
| 10 |
> I don't mind terribly when I have to edit an existing ebuild with long |
| 11 |
> lines, but *please* don't ask me to write them like that. |
| 12 |
> |
| 13 |
> Continuations can make the code more understandable when used |
| 14 |
> appropriately. And it's easy to write continuations that don't have any |
| 15 |
> problem with developers' tabbing preferences: |
| 16 |
> |
| 17 |
> ./configure \ |
| 18 |
> --prefix=/usr \ |
| 19 |
> --mandir=/usr/share/man \ |
| 20 |
> --infodir=/usr/share/info |
| 21 |
> |
| 22 |
> This might be considered overuse of line continuations, but it makes my |
| 23 |
> point; the code is readable, fits in a standard terminal, and has no |
| 24 |
> issues with tabs. |
| 25 |
> |
| 26 |
> Aron |
| 27 |
> |
| 28 |
|
| 29 |
im ok with this, much better than one line, and solve the align problem |
| 30 |
(although not as pretty ;-) |
| 31 |
|
| 32 |
|
| 33 |
-- |
| 34 |
|
| 35 |
Martin Schlemmer |
| 36 |
Gentoo Linux Developer, Desktop Team Developer |
| 37 |
Cape Town, South Africa |
Archives