> Then you have to set a cfargument for every possible variable that comes in > to your cfc
Yeah - I do that anyway really. Like Taco says required first & optional last. I've never really thought all these scenario's clearly, I've just always done it that way. I also generally use the object.method(argName=simpleValue, argName=simpleValue, argName=simpleValue) style and keep the values as simple & opaque as possible (i.e. not pass through complex structs if I can help it). I know everyone has their own ways of doing this but I just find that its better to be as verbose as possible, especially when working with CFC's because reuse is a major aim. In the couple of cases where I have used super() I've just been passing a single argument so I've done the super(arg) and had no issue - or maybe I did & thought I was wrong rather than CF when it didn't work??? -- 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/
