On 02/01/2014 11:27 AM, Luc Maisonobe wrote:
> Le 30/01/2014 23:23, Thomas Neidhart a écrit :
>> On 01/27/2014 09:13 PM, Thomas Neidhart wrote:
>>> On 01/27/2014 10:13 AM, Luc Maisonobe wrote:
Le 26/01/2014 23:52, Thomas Neidhart a écrit :
> Hi,
Hi Thomas,
>
> finall
Le 30/01/2014 23:23, Thomas Neidhart a écrit :
> On 01/27/2014 09:13 PM, Thomas Neidhart wrote:
>> On 01/27/2014 10:13 AM, Luc Maisonobe wrote:
>>> Le 26/01/2014 23:52, Thomas Neidhart a écrit :
Hi,
>>>
>>> Hi Thomas,
>>>
finally, I have a patch ready to be included for MATH-749.
>>>
On 01/27/2014 09:13 PM, Thomas Neidhart wrote:
> On 01/27/2014 10:13 AM, Luc Maisonobe wrote:
>> Le 26/01/2014 23:52, Thomas Neidhart a écrit :
>>> Hi,
>>
>> Hi Thomas,
>>
>>>
>>> finally, I have a patch ready to be included for MATH-749.
>>> What took me so long was some confusion about the type s
On 01/27/2014 10:13 AM, Luc Maisonobe wrote:
> Le 26/01/2014 23:52, Thomas Neidhart a écrit :
>> Hi,
>
> Hi Thomas,
>
>>
>> finally, I have a patch ready to be included for MATH-749.
>> What took me so long was some confusion about the type system in the
>> geometry package.
>>
>> It is actually
Le 26/01/2014 23:52, Thomas Neidhart a écrit :
> Hi,
Hi Thomas,
>
> finally, I have a patch ready to be included for MATH-749.
> What took me so long was some confusion about the type system in the
> geometry package.
>
> It is actually quite difficult to do some generic algorithm code by only
[...]
The Vector/Point interface does not allow access to its components,
thus
any algorithm that needs access to them either has to cast, or
explicitly specify the type.
[...]
Ideally, the Vector interface would have a method
double getComponent(int dimension)
or
double[] getData()
to p
Hi,
finally, I have a patch ready to be included for MATH-749.
What took me so long was some confusion about the type system in the
geometry package.
It is actually quite difficult to do some generic algorithm code by only
specifying the relevant space type (e.g. Euclidean2D).
The Vector/Point i