cfml

<@U0737EPFZ> trycf is having problems with this code with anything after acf 2021? <https://trycf.com/gist/b0e07b591aa59a7580f76e13d7aaab87/acf2021?theme=monokai> works on cffiddle

```{"message":"Complex object types cannot be converted to simple values.","documentation":"","pattern":"","line":0,"column":0,"state":"execution","error":"Complex object types cannot be converted to simple values.","html":"Complex object types cannot be converted to simple values.","stacktrace":"{\"Suppressed\":[],\"StackTrace\":\"coldfusion.runtime.CfJspPage$ComplexObjectException: Complex object types cannot be converted to simple values.\\n\\tat coldfusion.runtime.Cast._String(Cast.java:1410)\\n\\tat coldfusion.runtime.Cast._String(Cast.java:1348)\\n\\tat cfcfmler2ecfc340885392$funcPLAYCFMFILE.runFunction(/app/cfmler.cfc:85)\\n\\tat coldfusion.runtime.UDFMethod.invoke(UDFMethod.java:670)\\n```

yeah, there's a new feature in ACF that changes how function definitions are scoped and with the current setup it causes a duplicate definition error.  I haven't been able to allocate much time to it other than to diagnose.

you could do something like this instead for the time being:
<https://trycf.com/gist/edf3bbfbf9bd36df4fa6f267b46282eb/acf2021?theme=monokai>

I don't mind seeing stacktraces for errors

Interesting quirky thing with both engines is the support for meta data for args <https://dev.lucee.org/t/function-signature-issue/15185/4|https://dev.lucee.org/t/function-signature-issue/15185/4>

The stacktrace says the error occurs at Line 0, Column 0. That suggests the local environment (TryCF) may be interfering with the request somehow. This is confirmed by the fact that, on <https://cffiddle.org/|cffiddle>, that same code works on ColdFusion 2023 as well as on ColdFusion 2025.

<https://cffiddle.org/app/file?filepath=1103c727-2837-4a5f-82b1-800c7f56a9b2/ee35ee9e-008f-40a8-aa81-688d08ed277b/9eb48eeb-937d-46c2-963c-79449a252267.cfm|https://cffiddle.org/app/file?filepath=1103c727-2837-4a5f-82b1-800c7f56a9b2/ee35ee9[…]0a8-aa81-688d08ed277b/9eb48eeb-937d-46c2-963c-79449a252267.cfm>

Adobe_ColdFusion_2018.png

Adobe_ColdFusion_2021.png

Railo_4.2.png

BoxLang.png

Lucee_4.5.png

Lucee_6_Latest.png

Lucee_7_Beta.png

Adobe_ColdFusion_2025.png

Lucee_5_Latest.png

Adobe_ColdFusion_2023.png

Consider the test code:
`&lt;cfscript&gt;`
`function testFunction(){}`
`&lt;/cfscript&gt;`
`&lt;cfdump var="#variables#"&gt;`

You would expect the result to be a struct that has 'testFunction' as key. The code was therefore run on *TryCF* using

• the latest 4 Adobe ColdFusion versions (2018, 2021, 2023, 2025)
• the latest 4 Lucee versions (4.5, 5, 6, 7)
• BoxLang
• Railo 4.2
Only Lucee 6, Lucee 7 and Railo 4.2 yielded the expected result.

The results, in picture form, are as follows: