On 10/22/07, Matt Williams <[EMAIL PROTECTED]> wrote: > Not that I would want to, but it could be done via arguments.1, > arguments.2, etc.
Not legal variable names! Has to be arguments[1], arguments[2]. > I've always assumed (and that was my first mistake) that if the > argument wasn't declared in the function (via cfargument), then it was > somehow dropped or ignored. Yes I did know you can pass more arguments > than are declared, but again, I didn't know they were actually in the > function that was called. Ah, OK. Yes, if you declare, say, two arguments a and b and then pass three arguments, you'll have arguments["a"], arguments["b"] and arguments[3] - and you can reference the first two as arguments.a and arguments.b as well. > Until now, I didn't realize I was looping over more than just what I > declared, but anything within the struct returned by event.getArgs(). OK, I see where you're coming from. Yes, if you loop over the arguments array / struct (it's both) then you will see every argument passed, regardless of what is declared. -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
