> > But it's a *terrible* solution to a "problem" that most (all?) people > > wouldn't even encounter > >... > > trying to solve a non-problem >
> Let me get you straight on this, Sean. You are saying that not being able > to pass arg/value pairs to a method in the extended component is actually > not a problem? Well the question should be "what gains" do you get by having argumentCollection/arg-value pairs? It appears that its a nice way to bypass the CFARGUMENT tag altogether, and simply feed arguments down each layer as you go, until you hit a point where you have to break them apart for use (sooner or later, you have to make use of some specific argument). If that's the case, why bother having the objects extend one other, why not have a "Manager" of some kind, that literally has facade methods waiting for dynamic arguments, that it "then" feeds into specific object.methods. Also, Not knowing what arguments will come in/out of an objects inherited method to me sounds like a recipe for pain. It'd help if there was atleast a decent case study out there, to enlighten us poor folk who seem to fight the concept(s) merit(s). It Sounds like a lazy way out even for Coldfusion's standards is all i'm saying. If you have a hard-on for such feature, then why not have 1 argument routines, in that instead of going super.init() you could call super.initFromStruct(arguments) which carry out the same task, based on StructKeyExists or whatever blows your hair back. Scott. --- 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/
