I would presume this would be used only for the C++ API and/or the C++ utility headers.
On Mon, Jun 18, 2018 at 7:37 PM, Leif Hedstrom <zw...@apache.org> wrote: > > > > On Jun 15, 2018, at 2:21 PM, Jason Kenny <jke...@oath.com.INVALID> > wrote: > > > > This method works.. it is a lot easier if used with namespaces as the > "set" > > of changed objects are wrapped in a versioned namespace. This is a lot > > easier for a user to map to, then having a lot of different versioned > > objects. > > > I didn’t say it doesn’t work. I said it’s not worth the headaches. And, > these are C APIs, what you describe sounds like abstractions like COM for > objects ? > > Seems like no one else cares? If so, just do it. > > I’d insist that status quo should be retained, such that for the 99% of us > that just does #include <ts/ts.h>, things should just work as we expect, > and always get the version of the API(s) that are pertinent to that LTS > version I’m compiling against. And when we rev versions (from 7 to 8, or 8 > to 9), the defaults should change such that my plugins gets that get the > right version for that release. This implies that whomever implements this, > will be responsible for making sure that appropriate version updates are > done at all major versions, and removing the old versions etc. as needed. > > Ciao, > > — Leif > >
