When geometry is *not* by reference there are a number of optimizations that can be made by the implementation such as the use of OpenGL display lists which speed things up substantially.
You'll probably find that by-reference geometry is slower in most cases that not-by-reference.
Rob
Auguste Genovesio wrote:
I'm also very interested by the answer to this question !!!
Gili wrote:
Why does the majority of the API make copy of data instead of using it by reference which is far more efficiency? Surely this was a design decision of some kind, but what was the reasoning?
Thanks, Gili
===========================================================================
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".
-- A. Genovesio Quantitative Image Analysis Group Institut Pasteur 25, rue du Docteur Roux 75724 Paris Cedex 15
=========================================================================== 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".
--
Rob Nugent Sun Microsystems, Southampton, UK
[EMAIL PROTECTED]
Tel: +44 (0) 1489 585503 Fax: +44 (0) 1489 881363
=========================================================================== 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".
