<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaParaStyle">P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body fPStyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">
<p> </p>
<div style="FONT-FAMILY: Times New Roman; COLOR: #000000; FONT-SIZE: 16px">
<div>
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div>
<div style="FONT-FAMILY: Tahoma; DIRECTION: ltr; FONT-SIZE: 10pt">
<div style="FONT-FAMILY: Times New Roman; FONT-SIZE: 16px">
<div>
<div dir="ltr">
<div>
<div class="im">
<div>> b) Instead of inlining all the code for CollectRecordStaticVars how about outlining it into a couple of static functions?</div>
<div> </div>
</div>
<div>Hmm, yeah the body of that loop is basically "if static-member do this; else if field do that;" so factoring out those bits seems reasonable. (The lambda part, which I didn't touch, probably also could be factored out for similar reasons, but that might
exceed the scope of what I'm doing with this patch. Let me know.)</div>
<div class="im">
<div> </div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>> Yes please, thanks.</div>
<div> </div>
<div>It turns out to be infeasible to make these static functions, because they use private data and methods from class CGDebugInfo. Do you want me to do the outlining as new private methods, or just leave everything inline within CollectRecordFields? I will
say that the refactoring does make things look cleaner.</div>
<div>--paulr</div>
<div> </div>
<div> </div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>