Hi Francesco, Thanks for the confirmation, I was hoping that was the situation. Sorry for the poor phrasing.
What are your plans for the remaining steps before the back-merge, will that happen in the pdfmm repository or in a branch in the new podofo one? Cheers, Christopher The MathWorks GmbH | Friedlandstr.18 | 52064 Aachen | District Court Aachen | HRB 8082 | Managing Directors: Bertrand Dissler, Steven D. Barbo, Jeanne O’Keefe -----Original Message----- From: Francesco Pretto <cez...@gmail.com> Sent: Thursday, May 5, 2022 9:42 To: Christopher Creutzig <ccreu...@mathworks.com> Cc: Podofo-users <podofo-users@lists.sourceforge.net> Subject: Re: [Podofo-users] Future ABI stability of PoDoFo Hi Christopher, On Thu, 5 May 2022 at 08:16, Christopher Creutzig <ccreu...@mathworks.com> wrote: > > Backporting required parts of std::span and having a layer that switches > between std::format and fmtlib shouldn’t be too hard, assuming these are only > used internally and nothing in the API expects span inputs, for example. But > would we require contributors to use a C++20 enabled compiler? > > Please note that what you suggest it's already in place in pdfmm: I use fmtlib in place of std::format and a backported std::span. Thinking a little bit more about the topic, let's not argue too much about this: for the API/ABI surface I will just stick to C++17 requirement and hide the fact I'm using std::format and std::span. Cheers, Francesco _______________________________________________ Podofo-users mailing list Podofo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/podofo-users
