On 9/30/07, Mark Mandel <[EMAIL PROTECTED]> wrote: > Honestly, what I would really like - is if the auto getter and setter was > based off of a <cfproperty> declaration in the CFC, then you have something > that is document able, while still giving you the power to have getters and > setters that you don't have to write. If the <cfproperty> doesn't exist, > the auto get/set would throw an error.
Yup, definitely doable. In my upcoming article in FAQU, I talk about controlling the available get/set operations in various ways - Peter Bell uses a programmatic approach I believe, metadata (cfproperty) is another possibility. > Then you could add extra meta data > like '_privategetter="true"' to make getters or setters private, rather than > public (or something to that effect). Or perhaps just readonly="true" ? :) -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
