>> But... super.init( argumentCollection = arguments ) doesn't work due to a bug...
...yeah, I know.... and yeah, I know it's dumb to have this inconsistancy but is it that big a deal? as I said, VB (and other languages) do it all the time. Sure, argumentCollection is damn handy but at the end of the day you HAVE to know the API and give it what it needs. I mean, you can't use the object without the API.... the base CFC obviously has public methods with known arguments and known datatypes. Look at the component viewer - the argumnents are listed in the order expected - not alphabetical or anything else. maybe you should have a word to who made the base CFC and get them to put the required arguments first and optional last. not reading the API is akin to RTFM (or so was suggested to me by Scott Barnes...) is it REALLY a problem (as opposed to a slight inconvenience) - where reading the docs won't help you and naming the arguments (with "argumentCollection = struct" or "arg1='#val1#', etc") is infinitely better? methinks it's a storm in a teacup, Taco just 2c. barry.b -----Original Message----- From: Taco Fleur [mailto:[EMAIL PROTECTED] Sent: Thursday, 15 July 2004 12:40 PM To: CFAussie Mailing List Subject: [cfaussie] Re: super.method() But... super.init( argumentCollection = arguments ) doesn't work due to a bug... -----Original Message----- From: Barry Beattie [mailto:[EMAIL PROTECTED] Sent: Thursday, 15 July 2004 12:36 PM To: CFAussie Mailing List Subject: [cfaussie] Re: super.method() >> The ONLY way to do it is ordered values: >> super.foo(arg1, arg2, arg3) you mean if you're using optional arguments and doing this super.foo(arg1, , arg3, , , arg6) or similar? yeah damn stupid. happens in VB and VBS all the time - using the , as placeholders. HOWEVER (to play devils advocate here) you just have to be careful that the passed in struct super.init(argumentCollection = arguments ) matches the expected API - in both values AND names.... just 2c barry.b -----Original Message----- From: Adam Cameron [mailto:[EMAIL PROTECTED] Sent: Thursday, 15 July 2004 11:53 AM To: CFAussie Mailing List Subject: [cfaussie] Re: super.method() > I've never had an issue with it because I have never run into the bug myself :) Which is fair enough. > I'm not getting dragged into an argument about whether super.init( > argumentCollection = arguments ) is better than super.init( name = > value, name = value, name = value ), But that's the point... well it's *not* the point in this case. NEITHER of those two syntaxes work. Youca nnot name any arguments that you pass into a parent class' method, if using the super keyword. The ONLY way to do it is ordered values: super.foo(arg1, arg2, arg3) This works well in situations where all the arguments are known ahead of time, and are passed in in a prescribed order. We've a number of situations where this is absolutely not possible, which means that CF's weird implementation of CFC inheritance is useless to us. And accordingly... needs to be fixed. Adam --- 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/ Register now for the 3rd National Conference on Tourism Futures, being held in Townsville, North Queensland 4-7 August - www.tq.com.au/tfconf --- 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/
