sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris A. Mattmann (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SIS-70) Make QuadTreeNode and associated classes package private
Date Fri, 21 Dec 2012 07:01:15 GMT

     [ https://issues.apache.org/jira/browse/SIS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris A. Mattmann updated SIS-70:
---------------------------------

    Attachment: QuadTreeNode.patch

- patch from [~desruisseaux] on list.
                
> 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

Mime
View raw message