With some tricky symbolic links, I could probably arrive at a solution where these header would be exported (to plugins) in include/detail or something, not include/ts, so plugins writers would know not to include them directly.
On Tue, Mar 27, 2018 at 5:15 PM, Derek Dagit <der...@oath.com.invalid> wrote: > One reason this could be scary is that should we change any of these > headers going forward, it could mean a backward-incompatible release for > ATS. > > In-place upgrades may not be possible for administrators without > recompiling their plugins. > > On Tue, Mar 27, 2018 at 5:08 PM, Walt Karas <wka...@oath.com.invalid> wrote: > >> If we make BufferWriter.h available to C++ plugins, we would also have >> to make all of these header files available to plugins: >> >> MemSpan.h >> ink_assert.h >> BufferWriterForward.h >> ink_apidefs.h >> ink_error.h >> ink_std_compat.h >> ink_platform.h >> ink_config.h >> ink_autoconf.h >> >> Scary right? Or not so much? >> > > > > -- > Derek
