pdfbox-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Carrier (JIRA)" <j...@apache.org>
Subject [jira] Commented: (PDFBOX-422) Methods are marked as deprecated but they're effectively dead
Date Tue, 10 Feb 2009 22:02:00 GMT

    [ https://issues.apache.org/jira/browse/PDFBOX-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672419#action_12672419

Brian Carrier commented on PDFBOX-422:

The functions were renamed to make them more consistent with other functions and with their
actions.  The original names were kept to maintain backwards compatibility.  Can  you give
an example of how this breaks existing code?  

> Methods are marked as deprecated but they're effectively dead
> -------------------------------------------------------------
>                 Key: PDFBOX-422
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-422
>             Project: PDFBox
>          Issue Type: Bug
>          Components: Text extraction
>    Affects Versions: 0.8.0-incubator
>            Reporter: Gustavo Hexsel
> There are several methods on PDFTextStripper and PDFStreamEngine that are marked @deprecated,
but they are not really used by the existing infrastructure anymore.
> This would be ok if such methods weren't callbacks.  In this case, it breaks pre-existing
code, and prevents the compiler from letting you know the methods are not to be used anymore.
> Simply removing the methods would have been a much better solution in this case. 
> Example of said methods:
> org.apache.pdfbox.util.PDFTextStripper#processLineSeparator
> org.apache.pdfbox.util.PDFTextStripper#processWordSeparator
> org.apache.pdfbox.util.PDFTextStripper#writeCharacters

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message