[Bf-committers] post on coding in a large project

Shaul Kedem shaul.kedem at gmail.com
Wed Mar 29 11:34:25 CEST 2006


I agree.

Let's start a "code the structures" project.


On 3/26/06, Davide Vercelli <davide.vercelli at gmail.com> wrote:
>
> > Coding in a big project could look very intimidating. But its like
> > refitting a new door in a big house. You don't need to know what the
> > blueprint of the whole house looks like, you need to know only some
> > specific things about the hinges and the dimensions the door should
> > have.
>
> Sure. But my attempts to understand specific parts of the blender
> codebase are often hampered by non-commented struct fields... and I
> suspect that the meaning of many of them is evident to long-standing
> blender coders by analogy with other code (thus conflicting with the
> above statement). Sometimes I had to look into the python
> documentation in order to understand the meaning of some field, hoping
> for it to be exposed in python. Sure, looking for how the struct is
> used throughout the code helps, but maybe you could enforce some
> minimal comment policy with newly contributed data types. (It wouldn't
> harm to extend it also to new functions).
>
> UncleZeiv
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at projects.blender.org
> http://projects.blender.org/mailman/listinfo/bf-committers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://projects.blender.org/pipermail/bf-committers/attachments/20060329/94ddeb2d/attachment.html


More information about the Bf-committers mailing list