I've been trying to do useful things with the javax.vecmath package, and I 
must say, it does not provide the kinds of functionality I would expect from 
such a package.  Is there a reason that almost all the operations are 
destructive?  That is, the operation modifies the operand?

That makes the classes awkward to work with, but the difficulty of creating a 
Vector3f from a GVector (unless I'm not understanding something) is 
prohibitive. Creating a GMatrix with new GMatrix(double[]), but not new 
GMatrix(double[][]) makes no sense to me. The amount of code I have to write 
to work around these shotcomings is equal to the amount I whould have to 
write in order to accomplish the same thing without using the package.

Are there reasons these limitations exist?  What is the rationale for doing 
things in the very unnatural way?
-- 
STH
Hatton's Law: 
"There is only One inviolable Law."

==========================================================================To 
unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST".  For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".

Reply via email to