<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jun 12, 2009, at 2:00 PM, AlisdairM(public) wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><blockquote type="cite">-----Original Message-----<br></blockquote><blockquote type="cite">From: Chris Lattner [mailto:clattner@apple.com]<br></blockquote><blockquote type="cite">Sent: 12 June 2009 21:41<br></blockquote><blockquote type="cite">To: Ted Kremenek<br></blockquote><blockquote type="cite">Cc: AlisdairM (public);<span class="Apple-converted-space"> </span><a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a><br></blockquote><blockquote type="cite">Subject: Re: [cfe-dev] AST processing toolbox<br></blockquote><br><blockquote type="cite">Right. Another option is to pull in and "llvm-ize" libraries that are<br></blockquote><blockquote type="cite">really useful. For example, llvm/ADT/OwningPtr.h is a simple smart<br></blockquote><blockquote type="cite">pointer that is very similar to boost and other standard libraries.<br></blockquote><br>See my earlier reply <g><br>What would be most useful here is some small developer document pointing<br>out facilities are available through LLVM that we might find familiar.<br>Smart pointers, containers, other basic utilities, etc.<br></span></blockquote><div><br></div><div>Agreed, throughout LLVM/Clang the documentation can be greatly improved. We encourage everyone to submit patches for documentation where they feel it is lacking.</div><br><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><br>I have no problems with this approach, TR1 merely gives us some valuable<br>and reasonably well understood APIs. Nothing against providing self<br>hosted implementations if that is what is needed, at least for the<br>simpler components. I don't particularly fancy writing a pre-variadic<br>template version of tr1::function myself ;¬)<font class="Apple-style-span" color="#000000"><font class="Apple-style-span" color="#144FAE"><br></font></font></span></blockquote><br></div><div>Sounds good.</div></body></html>