search for: r80036

Albert Graef wrote: > I understand that. But in this specific case it would be very easy to > maintain, no? FWIW, suggested patch attached. That makes the LLVM 2.5 style raw_fd_ostream constructor work with the trunk (r80036). Note that this just adds a second constructor, existing code will continue to work as before. I'd be happy to prepare an analogous patch for the 2.6 release branch, just let me know. Albert -- Dr. Albert Gr"af Dept. of Music-Informatics, University of Mainz, Germany Email: Dr.Graef a...

On Aug 25, 2009, at 12:24 PM, Albert Graef wrote: > Trunk (r80020): > raw_fd_ostream(const char *Filename, std::string &ErrorInfo, > unsigned Flags = 0); > > It would be helpful to emulate the LLVM 2.5 variant of the constructor > on both 2.6 and trunk, so that frontend developers don't have to code > against three different versions of the

Chris Lattner wrote: > We do not guarantee API stability at all, so this is just the tip of the > iceberg. I understand that. But in this specific case it would be very easy to maintain, no? > It seems that it would be relatively easy to get autoconf to make a > include/llvm/Config/Version.h file that did this. I already have the necessary autoconf magic to deal with this in my

...Aug 25, 2009, at 3:40 PM, Albert Graef wrote: > Albert Graef wrote: >> I understand that. But in this specific case it would be very easy to >> maintain, no? > > FWIW, suggested patch attached. That makes the LLVM 2.5 style > raw_fd_ostream constructor work with the trunk (r80036). Note that > this > just adds a second constructor, existing code will continue to work as > before. I'd be happy to prepare an analogous patch for the 2.6 release > branch, just let me know. Hi Albert, Given that we don't guarantee backwards compatibility and prefer to k...