> Yes, that's all well and good. However, my original point, > which I didn't > make clear enough, is that when I write a program, that program should > explicitly accept specific inputs from specific locations. > This isn't a > documentation issue, it's a program design issue.
Specific inputs? yes. But specific locations? What's not appealing about being able to refer to the same URL variables you're used to, then at some point down the road, also being able to refer to that same variable coming from a form or even a custom tag without having to recode anything? If you're worried about looping through your form structure, you can still refer to it using the form scope - it's just also available in an attributes scope for further flexibility. I'm not trying to convert anyone or anything, it's all a matter of opinion I guess, but I would be interested in hearing of an example where the attributes scope gets in the way or ruins the design. Adam. ______________________________________________________________________ Why Share? Dedicated Win 2000 Server · PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation · $99/Month · Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusionc FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
