From 2f348d8b5d7d897ad44d192a2fd5f2b99b906c76 Mon Sep 17 00:00:00 2001 From: Campbell Barton Date: Sat, 24 Mar 2012 02:51:46 +0000 Subject: style cleanup: mainly for mesh code, also some WM function use. --- source/blender/bmesh/intern/bmesh_inline.h | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) (limited to 'source/blender/bmesh') diff --git a/source/blender/bmesh/intern/bmesh_inline.h b/source/blender/bmesh/intern/bmesh_inline.h index 6b529326607..2cfaf49d51e 100644 --- a/source/blender/bmesh/intern/bmesh_inline.h +++ b/source/blender/bmesh/intern/bmesh_inline.h @@ -68,8 +68,8 @@ BLI_INLINE void _bm_elem_flag_merge(BMHeader *head_a, BMHeader *head_b) head_a->hflag = head_b->hflag = head_a->hflag | head_b->hflag; } - -/* notes on BM_elem_index_set(...) usage, +/** + * notes on #BM_elem_index_set(...) usage, * Set index is sometimes abused as temp storage, other times we cant be * sure if the index values are valid because certain operations have modified * the mesh structure. @@ -78,8 +78,8 @@ BLI_INLINE void _bm_elem_flag_merge(BMHeader *head_a, BMHeader *head_b) * rather then adding inline loops, however there are cases where we still * set the index directly * - * In an attempt to manage this, here are 3 tags Im adding to uses of - * 'BM_elem_index_set' + * In an attempt to manage this, + * here are 5 tags I'm adding to uses of #BM_elem_index_set * * - 'set_inline' -- since the data is already being looped over set to a * valid value inline. @@ -96,6 +96,7 @@ BLI_INLINE void _bm_elem_flag_merge(BMHeader *head_a, BMHeader *head_b) * * - 'set_loop' -- currently loop index values are not used used much so * assume each case they are dirty. + * * - campbell */ #define BM_elem_index_get(ele) _bm_elem_index_get(&(ele)->head) -- cgit v1.2.3