I just made a test in CFMX 6.1 and Railo - it works as expected
So imho this bug was introduced with CFMX 7

-Harry

> -----Ursprüngliche Nachricht-----
> Von: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] Im Auftrag von John Farrar
> Gesendet: Freitag, 2. Dezember 2005 17:18
> An: [email protected]
> Betreff: RE: [CFCDev] CFMX Bug?
> 
> Isn't that just an "un-declared" argument?
> 
> John Farrar
> 
> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Harry Klein
> Sent: Friday, December 02, 2005 11:04 AM
> To: [email protected]
> Subject: [CFCDev] CFMX Bug?
> 
> 
> Testcode:
> ===========================================================
> <cfset testA(1)>
> 
> <cffunction name="testA">
>       <cfargument name="test">
>       <cfargument name="conflict" default="0">
>       
>       <cfset var myArgs = StructNew()>                
>       <cfloop collection="#arguments#" item="myKey">
>               <cfset myArgs[myKey] = arguments[myKey]>
>       </cfloop>
>  
>       <cfset testB(testArgs=myArgs)>
>       <cfset testB(testArgs=arguments)>       
> </cffunction>
> 
> <cffunction name="testB">     
>       <cfargument name="testArgs">            
>       <cfargument name="conflict" default="2">
>       
>       <cfdump var="#arguments#">
> </cffunction>
> 
> Output with <cfset testB(testArgs=myArgs)>:
> ===========================================================
> struct
> CONFLICT      2
> TESTARGS      
>       struct
>       CONFLICT        0
>       TEST    1
> 
> -> o.k., as expected
> 
> Output with <cfset testB(testArgs=arguments)>:
> ===========================================================
> struct
> CONFLICT      0
> TEST  1
> TESTARGS      
>       struct
>       CONFLICT        0
>       TEST    1
> 
> -> this is imho a bug, because:
>       "test" is not a argument in method "testB"
>       the value of the argument conflict should be 2 and not 0
> 
> -Harry
> 
> 
> ----------------------------------------------------------
> You are subscribed to cfcdev. To unsubscribe, send an email 
> to [email protected] with the words 'unsubscribe cfcdev' as 
> the subject of the email.
> 
> CFCDev is run by CFCZone (www.cfczone.org) and supported by 
> CFXHosting (www.cfxhosting.com).
> 
> An archive of the CFCDev list is available at 
> www.mail-archive.com/[email protected]
> 
> 
> 
> 
> 
> 
> ----------------------------------------------------------
> You are subscribed to cfcdev. To unsubscribe, send an email 
> to [email protected] with the words 'unsubscribe cfcdev' as 
> the subject of the email.
> 
> CFCDev is run by CFCZone (www.cfczone.org) and supported by 
> CFXHosting (www.cfxhosting.com).
> 
> An archive of the CFCDev list is available at 
> www.mail-archive.com/[email protected]
> 
> 
> 
> 


----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to 
[email protected] with the words 'unsubscribe cfcdev' as the subject of the 
email.

CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting 
(www.cfxhosting.com).

An archive of the CFCDev list is available at 
www.mail-archive.com/[email protected]


Reply via email to