You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sis.apache.org by "Chris A. Mattmann (JIRA)" <ji...@apache.org> on 2012/12/21 08:07:23 UTC
[jira] [Resolved] (SIS-70) Make QuadTreeNode and associated classes
package private
[ https://issues.apache.org/jira/browse/SIS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann resolved SIS-70.
----------------------------------
Resolution: Fixed
- patch applied to branch JDK6, JDK7 and trunk in r1424814.
> Make QuadTreeNode and associated classes package private
> --------------------------------------------------------
>
> Key: SIS-70
> URL: https://issues.apache.org/jira/browse/SIS-70
> Project: Spatial Information Systems
> Issue Type: Bug
> Components: geometry objects, storage
> Reporter: Martin Desruisseaux
> Assignee: Chris A. Mattmann
> Fix For: 0.3
>
> Attachments: QuadTreeNode.patch
>
>
> Martin provided a patch on list to make the QuadTreeNode, and Quadrant classes package private. This makes sense to me.
> From [~desruisseaux]:
> {quote}
> On a related question about QuadTree, I wonder if the QuadTreeNode class could be considered as internal mechanic? QuadTreeNode is used publicly only be QuadTree.getRoot(), itself used only internally be QuadTreeReader/QuadTreeWriter. Unless they are actually used by other projects outside SIS, could we turn the following into package-private elements?
> Method QuadTree.getRoot()
> Class QuadTreeNode
> Class Quadrant
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira