|
Richard, I agree that performance is a non-issue and getters/setters offer an opportunity to add your own hooks into a class. I am wondering why a getter or setter for a class variable changes the multi-threading issue. Most multi-threading issues I have run into are fixed by passing them as parameters and avoiding either direct access or access via getter/setter. David Morris >>> cujo@us.ibm.com 04/08/02 10:22PM >>> ...2) Later you start multi-threading something that you never worried about threading issues for initiallly. You start making various objects safe from the outside users and that is pretty easy, but you have all kinds of thread safety holes where two objects clobber each other's internal state from two threads that are allowed to execute at the same time... Richard D. Dettinger
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.