Jodi,
There is little you can do about this unless you wish to have your own alternate
API calls.
However, if you can isolate regions of code where you *know* something is not going to
change - then do one get and cache it
in a local variable and use that.
Then you can improve performance and have the best of both worlds. However, it
introduces potential errors if there is a source
of change that you don't know of.
Of course, this does not help with "setting". Your option here might be to
manage mutual exclusion and other low level API functions yourself where
you need to do high frequency get/sets. This is a bit of a scary thought as you
would need to have your own alternative to relevant parts of the API :(.
Chris
Jordi L�pez wrote:
> Hello,
>
> I appreciate your opinion on that:
>
> Java3D API is full of get* and set* methods and the most of them only copy
> the param value to its private atribute. The performance is lowered down
> with a lot of function calls in the stack. Most people says that making the
> inner state of an object public is not OO, but abusing of get and set
> methods isn't too (in my opinion), it's only a complicate and resource
> wasting way to do the same as with a simple dot. Maybe in future the inner
> attribute could change (then the getters and setters have meaning), but in
> most cases this changes never happen (a double will be always a double).
>
> I say that because I realise that one of the main issues with Java3D is
> performance, what do you think about? Maybe a red dot in javadoc meaning:
> "Use dot at your own risk!"
>
> Thank you in advance for your replies (and sorry for my language!)
>
> Jordi Lopez
> [EMAIL PROTECTED]
>
> ===========================================================================
> 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".
--
,--_|\
/ Oz \
Chris Thorne :)_.--._/
[EMAIL PROTECTED] v
===========================================================================
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".
