[LLVMdev] [cfe-dev] RFC: A Great Renaming of Things (or: Let's Repaint ALL the Bikesheds!)

[Chris Lattner]

One solution to this is to use "computed" #includes that come from macro expansions.

-Chris

On Nov 22, 2012, at 4:43 PM, Albert Graef <Dr.Graef at t-online.de> wrote:

> On 11/22/2012 12:07 PM, Chandler Carruth wrote:
>>> While the current naming may not be the best I'm -1 for the change in
>>>> general.
>> Are there any serious reasons or concerns? I'm well aware that this
>> will impose a cost on out-of-tree projects, but on the whole it should
>> be pretty minimal and consist of some applications of 'sed'.
> 
> Well, it's a bit more serious than that if an out-of-tree project tries
> to support older LLVM versions (e.g., Pure still supports all LLVM
> versions >= 2.5). Alas, most popular Linux distributions still package
> old LLVM versions (e.g., Ubuntu 12.04 LTS has LLVM 2.9, and this will
> still be around for a long time). That's something we poor out-of-tree
> projects just have to live with if we don't want to tell our users to
> compile their own LLVM from source.
> 
> I've learned how to live with the frequent C++ API changes, but in any
> case it would be nice if these name changes are documented meticulously
> so that 3.3 doesn't become a veritable nightmare for 3rd party projects. ;-)
> 
> Albert
> 
> -- 
> Dr. Albert Gr"af
> Dept. of Music-Informatics, University of Mainz, Germany
> Email:  Dr.Graef at t-online.de, ag at muwiinfa.geschichte.uni-mainz.de
> WWW:    http://www.musikinformatik.uni-mainz.de/ag
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev