new. =)
Chris Peterson
Gainey IT
Adobe Certified Advanced Coldfusion Developer
-Original Message-
From: Brian Kotek
Sent: Monday, July 09, 2007 10:27 PM
To: CF-Talk
Subject: Re: Init method and getters / setters in cfc
It's so trivial to generate the code for getters and setters that I
Well that isn't going to work for all variable types and seems a little
clumsy.
This method relies on top much which may not be present in a more complex
CFC application setup.
This e-mail is from Reed Exhibitions (Gateway House, 28 The Quadrant,
Richmond, Surrey, TW9 1DN, United Kingdom), a
Chris,
While I don't know what is *right*, here are the arguments that I have
heard against the generic getter/setter:
* The CFC is not self documenting. Looking at its functions does not
give you any insight into what it can set/get.
* Not clear on what should be returned if an invalid get is
Hal Helms uses the same style of coding you're talking about. A master get/set
method where you pass in the value AND name of the property you're trying to
access.
andy
-Original Message-
From: Peterson, Chris [mailto:[EMAIL PROTECTED]
Sent: Monday, July 09, 2007 2:52 PM
To: CF-Talk
I would add your component is now completely mutable. A developer can
add any data they want which may or may not be a big deal depending on
ones thinking on such things and what the component is meant to do.
An example that shows this code is going to accept any and all input
such as this.
Skinner
To: CF-Talk
Sent: Mon Jul 09 21:25:16 2007
Subject: Re: Init method and getters / setters in cfc
I would add your component is now completely mutable. A developer can
add any data they want which may or may not be a big deal depending on
ones thinking on such things and what the component
: Tuesday, 10 July 2007 6:25 AM
To: CF-Talk
Subject: Re: Init method and getters / setters in cfc
I would add your component is now completely mutable. A developer can
add any data they want which may or may not be a big deal depending on
ones thinking on such things and what the component is meant
It's so trivial to generate the code for getters and setters that I don't
really see the point in having generic getters and setters like this. As Ben
says, you lose the API for your component. You have no type checking (if
that's your thing). You lose the ability to seamlessly change the getter
8 matches
Mail list logo
