Re: [AGG] source code style

[Stephan A. <sup...@gm...>]

Hi,

Von: Jim Barry <ji...@ch...>
> > But for now, I vote to simply adopt the boost source code style.
> 
> Boost style is generally OK, though the 80-char max line length sucks 
> (especially with proportional fonts) and as you know I much prefer tab 
> indentation (so much easier to move around the code with the cursor 
> keys). But if you're going to insist on using spaces then 2 spaces per 
> indent is the way to go.

I have no idea yet what the boost style is, I just hope it doesn't try to encode the type into variable names, which I find greatly reduces readability. In any case, I am a great fan of a hard 80 char/line limit. Nothing worse than having to scroll horizontally. Not only in the code editor, but also in mail readers when reading commit notifications. Or in the browser when reading patches...

The very simple and strong argument pro a hard 80 char/line limit is that horizontal scrolling sucks. Thus there ought to be "some" limit, since we all have different coding environments and eventually without a limit, someone else is going to have to scroll. So why not use a widely established limit like 80 chars per line which will work well in other use cases as well. And no, a soft limit is no good either. :-)

In any case, discussions about the perfect style have a great potential to go out of hand, so I will try to constrain myself... :-D

In general, though I am perfectly happy with the AGG coding style. Changing an entire code base with a decent style to another style could also be considered a waste of time.

Best regards,
-Stephan