Open Heinenen opened 3 months ago
It is ok to removing pom_parser to avoid doubled work when implementing new parser features. Parser code using pom_parser has better readability.
Ok, thanks for your feedback. As long as no major additional work or bugs come up, we can probably keep it in and make the final decision only when necessary.
@J-F-Liu I would like to get your opinion on removing pom_parser, or at least deprecating it. A concrete problem that prompted this issue is described in https://github.com/J-F-Liu/lopdf/issues/125#issuecomment-2275055483.
248 probably has the same cause, but the PDF link expired, so I can't check that.
The main advantages we would get when removing one of the parsers:
It seems that the nom_parser is the better implementation of the two parser, at least in terms of performance (according to #60 and #208).