> In CFMX 6.1, it is not feasible to cfinclude your method > body. I'm not > sure how I feel about that yet.
I think its not such a bad "bug". Thought that was only applicable to the <cfreturn> tag...? > > Stace, there's nothing wrong w/ "this" anymore. > > Hmm, well, it's public data and so it has all the things > wrong with it > that public data has (lack of encapsulation being the primary > problem). But, essentially, all this does is allow us to access a property like this right?? <cfset foo = myCFCInstance.foo /> Instead of: <cfset foo = myCFCInstance.getFoo() /> I don't see that as being such an evil thing really. The major benefit I see to having an "instance" struct is the nice way to serialize instances notsomuch the enforcement of property access. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
