[tuhopuu-devel] Re: [tuhopuu-cvs] CVS commit: tuhopuu3/source/blender/hemesh/intern HE_ErrorState.c HE_EulerOperations.c HE_Event.c HE_Lib.c tuhopuu3/source/blender/hemesh/tools tool_average.c tool_bridge.c tool_del.c tool_drag.c tool_edgesharpen.c tool_extrude.c tool_hide.c tool_joinface.c ...

[joeedh]

Chris Want wrote:

>
> Hi Jonathan,
>
> This is a violation (for the most part) of Blender coding
> standards -- it *is* perfectly valid C. In fact, I don't
> always follow this practice in my personal projects.
>
> Four reasons that I can think of why it good to enforce
> this standard in tuhopuu:
>
> * Each C file only sees symbols that it actually needs
> to compile.
>
> * With this standard, it becomes clear to see what components
> a C file needs by quickly scanning the include statements.
>
> * Think of how much longer each C file would take to compile
> if we had one mega header called, say, Blender.h that
> included everything.
>
> * This is (with a few exceptions) the standard adopted by
> the bf tree. Staying compatible makes life easier for those
> who wish to patch their code over to that tree, and for
> those that merge the trees.
>
ok, I will stick to blender standard for now.

joeedh