Hi, Daniel Wilson schrieb: >>> If the library doesn't allow access to these objects > it'll be a significant blow to the capabilities of PDFBox. > > Certainly. Is restricting access (e.g. changing public objects/methods to > private/protected) even what's being proposed? > > That would be one of the simplest ways to break a lot of client > applications. No, I don't think so. But if we talk about public APIs, we have to define them. That doesn't lead to the converse argument, that everything, which isn't part of a public API has to be protected.
There are a lot of users just using these public APIs and we have to ensure that they don't have to change there code with every minor version of pdfbox. Those who dig down to the deep of pdfbox have to check on every new version if there are any relevant changes. If there are things people do by digging down into the deep, which are interesting for others, then we should implement that feature somewhere at a more public place, see e.g [1] or [2] BR Andreas Lehmkühler [1] https://issues.apache.org/jira/browse/PDFBOX-532 [2] https://issues.apache.org/jira/browse/PDFBOX-505
