search for: 023505

Displaying 6 results from an estimated 6 matches for "023505".

Did you mean: 023005
2009 Jul 15
2
[LLVMdev] LLVMContext: Suggestions for API Changes
...Change: LLVMContext" will probably get my attention while >> "Multi-threading support for LLVM" will not. > > How about a subject line "[LLVMdev] MAJOR API CHANGE: LLVMContext"? You mean like this subject ? http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-June/023505.html -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090715/a6884799/attachment.html>
2009 Jul 15
0
[LLVMdev] LLVMContext: Suggestions for API Changes
On Jul 15, 2009, at 10:56 AM, Jean-Daniel Dupas wrote: > > You mean like this subject ? > > http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-June/023505.html > Notice the sender line on that email... ;-) --Owen -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090715/ac8d3f6f/attachment.html>
2009 Jul 15
4
[LLVMdev] LLVMContext: Suggestions for API Changes
Owen Anderson wrote: > On Jul 15, 2009, at 10:56 AM, Jean-Daniel Dupas wrote: >> >> You mean like this subject ? >> >> http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-June/023505.html > > Notice the sender line on that email... ;-) Yes, you indeed announced that change, but as John rightfully remarked, the announcement gave little detail. For LLVM users like me, who just, well, *use* LLVM, this wasn't enough. Maybe it's not time to document the changes yet,...
2009 Jul 15
0
[LLVMdev] LLVMContext: Suggestions for API Changes
...Jul 15, 2009 at 2:24 PM, Albert Graef<Dr.Graef at t-online.de> wrote: > Owen Anderson wrote: >> On Jul 15, 2009, at 10:56 AM, Jean-Daniel Dupas wrote: >>> >>> You mean like this subject ? >>> >>> http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-June/023505.html >> >> Notice the sender line on that email... ;-) > > Yes, you indeed announced that change, but as John rightfully remarked, > the announcement gave little detail. For LLVM users like me, who just, > well, *use* LLVM, this wasn't enough. Maybe it's not time to...
2009 Jul 15
0
[LLVMdev] LLVMContext: Suggestions for API Changes
On Jul 15, 2009, at 9:53 AM, John Criswell wrote: > Owen Anderson wrote: >> On Jul 15, 2009, at 7:44 AM, John Criswell wrote: >> >>> 1) If technically possible, add the new API first, get it working, >>> email >>> llvmdev describing the old and new APIs, provide some lead time for >>> people to change over, and then remove the old APIs. This
2009 Jul 15
3
[LLVMdev] LLVMContext: Suggestions for API Changes
Owen Anderson wrote: > On Jul 15, 2009, at 7:44 AM, John Criswell wrote: > >> 1) If technically possible, add the new API first, get it working, >> email >> llvmdev describing the old and new APIs, provide some lead time for >> people to change over, and then remove the old APIs. This makes it >> easier to plan when I fix problems due to LLVM API changes