Thanks for the link Sean-- that was a good read. I especially like the last part of the article.
Getter/setter methods often make their way in code because the coder was > thinking procedurally. The best way to break out of that procedural mindset > is to think in terms of a conversation between objects that have > well-defined responsibilities. I am amazed at how much "psudo OO" code I have been seeing lately, it seems like the rush to learn OO has many coders putting procedural code in components and passing data and objects around like candy. I was always off-put by using getters in my view, or anywhere for that matter, I developed a habit of referencing the attributes/variables structures with the event/myFusebox beans in my objects with FB5 and I always was happy with the results. It always made more sense than calling a getter on a bean from the dark corners of my apps. -- /Kevin Pepperman "They who can give up essential liberty to obtain a little temporary safety, deserve neither liberty nor safety." - Benjamin Franklin -- You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en.
