Re: [AGG] source code style

[Vinnie <th...@ya...>]

> Changing an entire code base with a decent
> style to another style could also be considered a waste of
> time.

I agree. Going through and reformatting all the source code just to conform to some arbitrary new style is probably not the best use of time.

However, it is the case that as new code gets contributed, or existing code is modified, one must either try to preserve the tabbed horizontal formatting style, change the style to conform to something new, or fuss with their editor to get things to look right.

Therefore I propose the following:

- A new style is recommended for agg. Based on the feedback in other threads on this subject, something that is boost style-like (but not exactly) is desirable. For example, never using tabs. But maybe we don't need to be so strict on placement of the opening brace.

- The new style is used for all submitted new source files

- The new style is used for code added to existing source files, with the author having the option to reformat the entire modified source file, just the portion they submitting, or something in between (for example, reformatting just the function containing a change, or just the class in a multi-class file).

- Existing files which have not been modified will not be reformatted. This will have the secondary beneficial effect of providing clues to the reader for the how long its been since code was touched.