[Box Backup] Coding standards

Martin Ebourne boxbackup@fluffy.co.uk
Thu, 01 Sep 2005 20:55:11 +0100

On Thu, 2005-09-01 at 12:33 -0700, Gary wrote:
> > No overloading of operators, especially not for i/o. Only exception
> Once I read the subject, I knew this was gonna be in here ;) j/k.
> > Indent with tabs, with 4 character tab stops.
> > Bracing style: (...)
> I think every programmer is most efficient and produces least bugs when
> he or she is using his or her own code-style and idioms (within reason,
> of course). We could always use an automated source code styler to
> bring everything into a uniform code universe.

The trouble with gnu indent and the others is that they tend to mess up
the difficult indenting - especially when statements are split over
lines. That's ok as a one off because they get fixed manually, but as a
repeated process the complex alignments wouldn't be fixable.