With all due respect to all you far more OO-seasoned gentlemen than I,
this isn't the response I expected. Here's what I was thinking:
- On a gut level, though I appreciate the value of an object that
hides its internals completely and provides no access to them other
than through its methods, it
About the only use for getMemento() method I have is as a kind of
CFDUMP of the current data contained within an object. As a
debugging device to check that the values of the various parameters
actually are what i think they should be.
In that case, the getMemento() method should always ret
On Sun, Nov 14, 2010 at 11:03 AM, Dave Merrill wrote:
> In the cfproperty-oriented world, where properties get dumped into the
> variables scope along with your methods and anything else there, many
> folks including me have written getMemento methods to return a struct
> with the values of the o
"Should a getMemento method return the results of getters if they exist?"
I believe so, but backwards.
Sorry.. Couldn't resist.
~|
Order the Adobe Coldfusion Anthology now!
http://www.amazon.com/Adobe-Coldfusi
In the cfproperty-oriented world, where properties get dumped into the
variables scope along with your methods and anything else there, many
folks including me have written getMemento methods to return a struct
with the values of the object's declared properties, only.
Do you suppose methods like
5 matches
Mail list logo
