Aspell Developer’s Manual: Style Guidelines
Description: Aspell spell checker developer’s manual.

Next: How to Submit a Patch, Previous: Top, Up: Top [Contents]

## 1 Style Guidelines

* Style Guidelines:: * How to Submit a Patch:: * C++ Standard Library:: * Templates:: * Error Handling:: * Source Code Layout:: * Strings:: * Smart Pointers:: * I/O:: * Config Class:: * Filter Interface:: * Filter Modes:: * Data Structures:: * Mk-Src Script:: * How It All Works:: * Copying::

As far as coding styles go I am really not that picky. The important thing is to stay consistent. However, please whatever you do, do not indent with more than 4 characters as I find indenting with more than that extremely difficult to read as most of the code ends up on the right side of the screen.