>> Its a matter a of consistency in the language. fair enough
>> Debates about which method of passing arguments is better practice are >> not relevant to this thread. just so people realise that argumentCollection=args is a bit of a luxury. CF is the only language I've come across that can do this and, since the NAMES of the args have to be right, has gotcha's all it's own. thread closed? cheers barry.b -----Original Message----- From: Mark Stanton [mailto:[EMAIL PROTECTED] Sent: Thursday, 15 July 2004 1:38 PM To: CFAussie Mailing List Subject: [cfaussie] Re: super.method() Barry I think the point is that I can do: <cfset someObject = createObject('component','com.gruden.someObject')> <cfset arg1 = "argument 1"> <cfset arg2 = "argument 2"> <cfset arg3 = "argument 3"> <cfset args = structNew()> <cfset args.arg1 = arg1> <cfset args.arg2 = arg2> <cfset args.arg3 = arg3> And... <cfset foo = someObject.bar(argumentsCollection=args)> <cfset foo = someObject.bar(arg1, arg2, arg3)> <cfset foo = someObject.bar(arg1=arg1, arg2=arg2, arg3=arg3)> ...will all do the same thing. But if I have a call to super.bar() within the someObject.bar() I don't have this flexibility. I can ONLY use the: <cfset super.bar(arg1, arg2, arg3)> ..syntax. Its a matter a of consistency in the language. Debates about which method of passing arguments is better practice are not relevant to this thread. -- 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/
