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).
In java3d object you see are wrappers around real data. This set/get
method do not only set actual value in back tier, but also check for
capability bits/compiled state, synchronize changes with rendering
thread and perform some other magical stuff. A lot more than simply set
a value.
Artur
===========================================================================
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".
