This becomes an issue however, when translating onMissingMethod calls to actual method calls -
if you want to pass through the arguments that come through onMM, they can come through as arg[1], arg[2] etc, as they weren't named when they were called. This means you have to translated the positions to the names through meta data, which is a very annoying process, and puts extra strain on the system. If we could just call methods through cfinvoke with unnamed variables, but with positions, that would be very, very handy. Mark On 10/23/07, Brian Kotek <[EMAIL PROTECTED]> wrote: > I'd argue that the better solution would be just to add a cfargument tag to > the target method(s). > > On 10/22/07, Baz < [EMAIL PROTECTED]> wrote: > > Hi gang, > > > > I was wondering if it were possible to pass an un-named argument to a > dynamic function. For example, I have this call: > > > > > > <cfinvoke method="get#arguments.Name#" returnvariable="ReturnValue" > value="#arguments.Value#" /> - It is a CFINVOKE because to my knowledge, in > CF8, you still can't invoke a dynamic function using script, i.e. > set#DynamicFunction#(arguments) The attribute "value" in the cfinvoke call > basically passes the invoked function an argument named "Value". Is it > possible to pass in an un-named argument in position 1 instead? Basically > the equivalent of set#DynamicFunction#(Value)?? > > > > Cheers, > > Baz > > > > > > > > > > > > > > > -- E: [EMAIL PROTECTED] W: www.compoundtheory.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
