So you'd be happy with it the way it is if I took out the mem-clear and the normalization<div>thus getting rid of the ability to iterate over the vertices?</div><div><br></div><div><br><br><div class="gmail_quote">On Tue, Mar 15, 2011 at 7:22 AM, <span dir="ltr"><<a href="mailto:brechtvanlommel@gmail.com">brechtvanlommel@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On 2011/03/15 14:10:45, mikkelsen7 wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
We can change anything we want in there. Angle weighed, not angle<br>
</blockquote>
weighted,<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
check for degenerate prims, whatever. Anything we might ever want to<br>
</blockquote>
add or<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
remove<br>
from the method is now confined to one place which is a huge plus.<br>
</blockquote>
<br></div>
Well, I don't think we should account for everything you might possibly<br>
want to do, but it's not even clear what you might need this abstraction<br>
for in the future. All these examples you give can be done inside a<br>
function like accumulate_vertex_normals.<br>
<br>
These iterators are hard to follow & debug, I much prefer readable<br>
slightly duplicated code over this.<div><div></div><div class="h5"><br>
<br>
<a href="http://codereview.appspot.com/4280049/" target="_blank">http://codereview.appspot.com/4280049/</a><br>
</div></div></blockquote></div><br></div>