> What is the problem with using CFC this. variables? > > ... > > Yes, the getter/setter proponents seem to think a function call is > better CF and it is effective encapsulating. But for the code in me I > cannot figure out why. It just seems to me that getter/setter for > individual instance variables is a lot of extra runtime memory > allocations, that in itself can cause memory leaks or thread failures.
I don't see why calling a method of an object requires any more memory allocation than manipulating a public property of an object, but that's neither here nor there. The problem with using public properties is that they cannot be controlled by the object itself. It's my understanding that the object should be responsible for its own properties, and that within an OO model your program should largely consist of objects sending messages to other objects by calling methods of those objects. If you can directly manipulate the properties of an object, why even bother having methods in the object at all? Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ phone: 202-797-5496 fax: 202-797-5444 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Special thanks to the CF Community Suite Silver Sponsor - RUWebby http://www.ruwebby.com Message: http://www.houseoffusion.com/lists.cfm/link=i:4:188804 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
