[
https://issues.apache.org/jira/browse/XERCESJ-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16461199#comment-16461199
]
KuiLIU commented on XERCESJ-1692:
---------------------------------
[[email protected]] Yes, changing the name of a public method could break
the backward compatibility. Maybe, making the method deprecated and creating a
new method is a choice of resolving this problem.
> Inconsistent method name
> ------------------------
>
> Key: XERCESJ-1692
> URL: https://issues.apache.org/jira/browse/XERCESJ-1692
> Project: Xerces2-J
> Issue Type: Improvement
> Reporter: KuiLIU
> Priority: Major
>
> The following method is named as "getIndenting", but the method checks
> whether the indentation is specified or not.
> So renaming the method as "isIndenting" should be more clear than
> "getIndenting".
> {code:java}
> /**
> * Returns true if indentation was specified.
> */
> public boolean getIndenting()
> {
> return ( _indent > 0 );
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
