--nextPart1353340.gYuuTvZfaC
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Le mercredi 23 ao=FBt 2006 12:38, Frerich Raabe a =E9crit=A0:
> And I suppose simply saying "You're free to indent the statements in a ca=
se
> branch of a switch if you want." is not acceptable by the coding style
> police? I don't want to start a flame war but I never quite understood why
> you have to define all such things to 100%, as long as common sense stuff
> like "Don't write the body of an if statement on the same line" or
> something like that is agreed on.
>
> I think if you have developers on a project who are more 'productive'
> because it's easier for them to understand code which has tiny cosmetic
> things like indented case statements, then you have bigger problems than =
an
> inconsistent indentation style. :-}

+1

I think that the space vs. tab,  and the number of space per indentation is=
 an=20
important thing.  Because code becomes unreadable if indentation is not=20
correct.

Anyway, the number of space around the '=3D' sign or parenthesis doesn't re=
ally=20
mater.

Personally, I'd just like a indenting policy,  not a strong coding style=20
policy.

--nextPart1353340.gYuuTvZfaC
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQBE7Dfiz58lY8jWrL0RAvOkAJ9hjwOFP3vW8n1ZSJgcpvNK1wWQVQCfdza+
ezR300CnAtAe9pVTEJW3mJk=
=/8ct
-----END PGP SIGNATURE-----

--nextPart1353340.gYuuTvZfaC--