<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jun 3, 2011, at 3:36 PM, Douglas Gregor wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jun 3, 2011, at 3:33 PM, Jonathan Turner wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jun 3, 2011, at 3:16 PM, Douglas Gregor wrote:<span class="Apple-style-span" style="color: rgb(100, 1, 4); "> </span></div><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div><br></div><div>Sure, but as long as it always puts *something* into the record, we should be fine.</div></div></div></blockquote><div><br></div><div>Good point. As long as we can assume that TypedefDecl will always have some TypeSourceInfo, we're fine. I've added an assertion to note this. If that's sounds good, I'll check in.</div></div></div></blockquote></div><br><div>Why is TypedefDecl special in this regard? My assumption is that, if the TypeSourceInfo* is NULL, we'll just end up writing out one element in the VBR array that says "it's a NULL pointer". Is that not true?</div></div></blockquote></div><br><div>Ah, now I see your point. Yes, you're right, it doesn't matter. They're fixed now.</div><div><br></div><div>Jonathan</div></body></html>