<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>Le 15 juil. 09 à 20:26, John Criswell a écrit :</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Owen Anderson wrote:<br><blockquote type="cite"><br></blockquote><blockquote type="cite">On Jul 15, 2009, at 9:53 AM, John Criswell wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">Owen Anderson wrote:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">On Jul 15, 2009, at 7:44 AM, John Criswell wrote:<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">1) If technically possible, add the new API first, get it working, <br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">email<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">llvmdev describing the old and new APIs, provide some lead time for<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">people to change over, and then remove the old APIs. This makes it<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">easier to plan when I fix problems due to LLVM API changes and when I<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">can work on our own bugs. :)<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">The high-level change was already described and discussed on LLVMdev.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">First, did you discuss it or announce it? There's a difference.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">With its high traffic volume, I don't read all llvmdev mails anymore. I<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">pick and choose based on their subject lines. A subject entitled "API<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Change: LLVMContext" will probably get my attention while<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">"Multi-threading support for LLVM" will not.<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">How about a subject line "[LLVMdev] MAJOR API CHANGE: LLVMContext"?<br></blockquote>Yes, that particular message fits the first criterion: it announces the<br>change in the subject line. I thought you might have been referring to<br>other emails about LLVMContext that I didn't see, but you weren't; you<br>were referring to the above message.<br><br>However, IMHO, the message from June doesn't clearly state what is to<br>change. It tells me static methods will be removed, but it doesn't tell<br>me where they are re-implemented. It assumes I can infer that by<br>understanding how LLVM uniques values.<br><br>-- John T.<br></div></blockquote></div><div><br></div>Wasn't this tips not enough ?<div><br><div>"<span class="Apple-style-span" style="font-family: monospace; white-space: pre; ">To ease this transition, I have added a getGlobalContext() API. If </span></div><span class="Apple-style-span" style="font-family: Times; "><pre>you're only ever planning to use LLVM on a single thread, it will be
completely safe to simply pass this value to every API that takes an
LLVMContext."</pre><pre><br></pre><pre><br></pre></span></div></body></html>