From: Mark Rogers <mark.rog...@powermapper.com> > tl;dr > PoDoFo needs a general mechanism to prevent recursive stack consumption > because this can happen in many different places in PDFs. Even if the issues > above are fixed there will still be other stack overflow issues in PoDoFo.
I agree. But I would like to propose yet another potential solution: 4) Parsing PDF does not create an unbounded number of different objects. Quite the opposite: Resolving the same indirect reference for the second time results in exactly the same object as the first time; semantically, the PDF file just has another edge coming into it. Therefore, we may want to have a cache of resolved references. If there are cases where the same object in the PDF file needs to be represented by multiple PoDoFo classes, the cache may need to be able to store these several representations. Whether trying to resolve a reference currently under construction should throw a “recursive definition” error or provide a handle that is going to update as needed is something to discuss. Does this make sense? Cheers, Christopher The MathWorks GmbH | Friedlandstr.18 | 52064 Aachen | District Court Aachen | HRB 8082 | Managing Directors: Bertrand Dissler, Steven D. Barbo, Jeanne O’Keefe
_______________________________________________ Podofo-users mailing list Podofo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/podofo-users
