On Thu, 2018-12-06 at 09:09 +0100, Olivier Mascia wrote:
> > I'd remove the std::auto_ptr usage from the public
> > API completely, and use, if needed, either of them based on the
> > compiler being used (and what it offers) only in internal code.
> > That
> > would support both old and new C++ standards.
>
> It wouldn't work. There is no point in having an option to compile
> internal code with (auto|unique)_ptr when interfaces would use
> unique_ptr. Because unique_ptr support would then be required for
> internal code anyway, so why would it need to insist on using
> auto_ptr in some places? :)
Hi,
I said:
a) remove from public API,
b) use in private API, only if needed.
It's not the same as what you object to. It doesn't matter what is used
internally, when it doesn't touch public API.
Bye,
zyx
_______________________________________________
Podofo-users mailing list
Podofo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/podofo-users
