In CFMX 6.1, it is not feasible to cfinclude your method body. I'm not sure how I feel about that yet.
As I said, this should say "it is now feasible" and I'm not sure how I feel about cfinclude'ing method bodies.
Hmm, I am doing a lot of
<cffunction name="getObject" output="0" access="public"> <cfargument name="cfcObject" required="1"> <cfargument name="objectID" required="1">
<cfset stArgs = arguments> <cfinclude template="_dbpersistor/getobject.cfm"> <cfreturn true> </cffunction>
You get code that can't call other methods in the same instance (because stArgs is in the unnamed scope and shared by all functions).
Also, using 0 and 1 instead of false and true is obtuse and not considered good practice.
Just because I don't like scrolling in long scripts..;)
Then write smaller CFCs :)
Seriously, refactor your code so that your components aren't so long...
Is this bad codingstyle in 6.1 ?
It's certainly bad style in 6.0 (because you have to hack around bugs with arguments scope etc) - I'm not yet convinced it becomes any better in 6.1...
Sean A Corfield -- http://www.corfield.org/blog/
"If you're not annoying somebody, you're not really alive." -- Margaret Atwood
----------------------------------------------------------
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).
