[Bf-committers] line length / code style.

Ton Roosendaal ton at blender.org
Tue Dec 20 19:27:18 CET 2011


> c'mon! - http://www.graphicall.org/ftp/ideasman42/long_lines.png

That's not a good example.

Some of these long lines are great to be in 1 line; because they're  
just not meant to be read as code really (it's data, a long string, or  
just lot of crap).

The "rule" for line length is not about numbers (80 or 120) but about  
producing readable code, emphasizing structure and functionality and  
to assist debugging. A developer can use own insights and style to  
follow this in sane ways.

For that reason, the line length rule is not a rule (like always  
capitalize #defines) but an important guideline; follow it to produce  
readable code, based on your insights for it.

Splitting the code guide in "Rules" and "Guides" would be also helpful  
to prevent lengthy discussions.

You know; "strict in what we agree on, freedom in our doubts, love for  
all!" :)


Ton Roosendaal  Blender Foundation   ton at blender.org    www.blender.org
Blender Institute   Entrepotdok 57A  1018AD Amsterdam   The Netherlands

On 20 Dec, 2011, at 0:12, Campbell Barton wrote:

> one of the things I was worried about, looks like it might be  
> happening...
> - not content to set basic rules, devs want full style guide.
> - devs can't agree
> - nothing happens
> So if we cant get our act together in under a month or so (or if Ton
> is busy, since it seems Ton wants to handle this now) - whatever the
> reason,
> I'd like to go ahead with some sane line length (120, and apply this
> rule where it makes sense).
> c'mon! - http://www.graphicall.org/ftp/ideasman42/long_lines.png
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers

More information about the Bf-committers mailing list