Then you have to set a cfargument for every possible variable that comes in to your cfc
What is something isnt required and doesnt get passed in? doFunc(arg1, arg2, arg3, arg4) the third argument isnt required, and cause it isnt required, it may not get passed in <cfargument name="arg1" /> <cfargument name="arg2" /> <cfargument name="arg3" /> <cfargument name="arg4" /> I then call the function like this doFunc(arg1, arg2, arg4) now the cfc looks at the arguments and goes, "hey i only have 3 arguments, so I guess the last one is missing" and then it makes arguments.arg3 actually the value of arg4 Correct me if i am wrong about how that would work Steve -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Mark Stanton Sent: Thursday, July 15, 2004 3:43 PM To: CFAussie Mailing List Subject: [cfaussie] Re: super.method() Yeah - like Taco said... In the case of: <cfset foo = someObject.bar(arg1, arg2, arg3)> ...the value of #arg1# would be assigned into whatever your first <cfargument> was within the bar() function. When you do it this way the order of the items within () and the <cfargument> statements becomes really important. -- Mark Stanton Gruden Pty Ltd http://www.gruden.com --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/ --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
