Well I think passing attributes by name is a good idea. If you change the interface to your code then the code that is using that interface will generally need to change as well.Passing attributes by name worries me and goes against the way I work. This tightly couples the calling code to the tag.
If you passing the arguments unnamed via a list and you change the number of arguments and or order of arguments you could introduce subtle bugs into your system without knowing it. If you named your arguments you would get a nice concise error along the lines of 'variable x' undefined.
Naming arguments makes you think about the design of the interface to your tag [or cfc] and you're less likely to make mistakes when using it and it makes other people easy to understand your code.
You want to abstract the interface from your code internals but I don't think you should abstract the interface itself, a tight coupling with the interface is a good thing, a tight coupling with the internals of the code is a bad thing.
Just my opinion anyway.
Justin ============================================= Justin Mclean Class Software Phone: (02) 93321230 9 Chapman St Fax: (02) 9475 0073 Surry Hills Mobile: 0416 119 342 NSW 2010 =============================================
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
MX Downunder AsiaPac DevCon - http://mxdu.com/
