<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Oct 9, 2007, at 3:04 PM, Tanya Lattner wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; 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: 0; "><br>On Oct 9, 2007, at 2:38 PM, Ted Kremenek wrote:<br><br><blockquote type="cite">Author: kremenek<br></blockquote><blockquote type="cite">Date: Tue Oct 9 16:38:09 2007<br></blockquote><blockquote type="cite">New Revision: 42813<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">URL:<span class="Apple-converted-space"> </span><a href="http://llvm.org/viewvc/llvm-project?rev=42813&view=rev">http://llvm.org/viewvc/llvm-project?rev=42813&view=rev</a><br></blockquote><blockquote type="cite">Log:<br></blockquote><blockquote type="cite">Added implementation of immutable (functional) maps and sets, as<br></blockquote><blockquote type="cite">implemented on top of a functional AVL tree. The AVL balancing code<br></blockquote><blockquote type="cite">is inspired by the OCaml implementation of Map, which also uses a <br></blockquote><blockquote type="cite">functional<br></blockquote><blockquote type="cite">AVL tree.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Documentation is currently limited and cleanups are planned, but <br></blockquote><blockquote type="cite">this code<br></blockquote><blockquote type="cite">compiles and has been tested.<br></blockquote><blockquote type="cite"><br></blockquote><br>You mention that documentation is limited, so this may be a stupid <br>question. Do you plan to add doxygen style comments to each function <br>providing a brief description of it?<br><br>Thanks,<br>Tanya</span></blockquote><br></div><div>Yes I do plan on adding doxygen comments. The focus will be on documenting the public interface first. The internal implementation is still being cleaned up.</div></body></html>