Patrick McElhaney said the following on 1/20/2006 12:29 PM:
On 1/20/06, Nat Papovich <[EMAIL PROTECTED]> wrote:
  
Is this all for the sake of saving keystrokes? A good IDE (like Eclipse with
Java classes) solves this problem in that you can highlight a class variable
and rt-click->add getters/setters. Most of the time, you just ignore all the
generated getters and setters, but when you want to add some code, the
methods are already there.

Seems like the problem is being solved in the wrong place.

    
I agree, Nat. This does seem to be about saving keystrokes. Then it's
retroactively justified with "Oh, but now I can do all this other
stuff." And that's fine, but I never wanted to do all that other
stuff.

In CFEclipse, you can create a getter/setter code template that's
accessable in as few as three keystrokes.

I always try to keep in mind that code will be read many times more
than it's written.

Patrick
  
I'm going to agree with this again.  Patrick is right -- other people have to read your code.  The problem I have with set() and get() -- even with custom methods that magically get run if matched -- that you lose "automatic" documentation of the structure of the bean.  Having a well defined API is important because it doesn't force me to remember the internal make up of data relationships.  This is especially important for development in Teams and lower level developers that most leverage the API and not actually architect the application.

Bill's message just came in -- for the record I'm not dogging Jim.  In the end, everybody get comfortable with their way of implementation and that is good because you're settling into a routine instead of doing everything willy-nilly every time you implement something.  I guess the problem for me is that I've found that most developers seriously do not document their applications well enough.  I try to always things that I'm not always going to the only person who sees this.  Documentation is hard to write and practice makes perfect as they say.  Personally, I would rather write out setters/getters (probably through a code gen) than spend time documenting what the bean is representing.  Accessors are very low level code IMHO and basically they should speak for themselves (CFC explorers are great!) unless you're doing something funky in them (i.e. write a hint...).

.Peter
-- 
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 [email protected] 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/[email protected]

Reply via email to