[ https://issues.apache.org/jira/browse/GEOMETRY23?page=com.atlassian.jira.plugin.system.issuetabpanels:commenttabpanel&focusedCommentId=16658414#comment16658414
]
Gilles commented on GEOMETRY23:

{quote}It seems unnecessarily verbose and I don't think the method is ambiguous
{quote}
The point is rather that a symmetric API (i.e. {{ofCartesian}} and {{ofSpherical)}} does some
effort (IMHO worth the additional typing effort) of hiding the implementation, which makes
it closer to mathematical "purity" (a vector is a vector, independently of the system in which
its coordinates are expressed), from the caller's perspective.
> Remove Euclidean Point Classes
> 
>
> Key: GEOMETRY23
> URL: https://issues.apache.org/jira/browse/GEOMETRY23
> Project: Apache Commons Geometry
> Issue Type: Improvement
> Reporter: Matt Juntunen
> Priority: Major
> Labels: pullrequestavailable
>
> Based on discussion of the current Point/Vector API in GEOMETRY14 and research into
other geometric libraries, I think we should remove the Euclidean Point?D classes and make
Vector?D also implement Point. This will end up being similar to the previous commonsmath
design but avoids the issue raised in MATH1284 since the Point and Vector interfaces are
not related. They just happen to be implemented by the same class, which we're calling Vector?D
since a vector can be used to indicate a point (by adding it to the origin).
> In the course of trying this out this design, I ended up removing 7 classes and simplifying
several methods. I think that's a good indicator that this is a good design choice.
>
> Pull request: https://github.com/apache/commonsgeometry/pull/15

This message was sent by Atlassian JIRA
(v7.6.3#76005)
