Re: [CFCDev] Bean and CFC question

[Peter J. Farrell]

Nat Papovich said the following on 1/20/2006 1:10 PM: Bill's message just came in -- for the record I'm not dogging Jim.    For the record, I'm not dogging Jim either. I'm dogging Hal and Sean for the same reasons Patrick mentioned. Code is maintained and read far more often that it's written. I *frequently* find myself devising cunning solutions to save keystrokes at the expense of simplicity. But I implement very few of those solutions because I know that this momentary effort expended on a relatively repetitious task is the right way to code, not the least mind-numbing.   So if you want to use super get("property"), then by all means do it. But make sure you're doing it for the right reasons.   NAT Agreed.  I find myself doing more complex things than needed.  Planning for future additions is different than saving keystrokes.  I'm know I'm sound like a broken record, but accessor methods (in general) follow such a "strict" format - it's silly not to use some sort of code generator. I particularly like the accessor method description at Wikipedia (http://en.wikipedia.org/wiki/Accessor_method): An accessor method is a kind of method that is usually small, simple and provides the means for the state of an object to be accessed from other parts of a program. Although it introduces a new dependency, use of the methods are preferred to directly accessing state data because they provide an abstraction layer. The key word to me is "provide an abstraction layer"...why would added another layer of abstraction (meaning an uber get() or set() methods with custom method lookup)?  I'm no OOP guru...any thoughts? -- Peter J. Farrell :: Maestro Publishing http://blog.maestropublishing.com Rooibos Generator - Version 2.1 Create boilerplate beans and transfer objects for ColdFusion! http://rooibos.maestropublishing.com/ - Member Team Mach-II - Member Team Fusion ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to cfcdev@cfczone.org with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/cfcdev@cfczone.org