Weird transaction issue with implicit struct (and possible array)

I had a look at this, and it's a variation of a bug we (Duncan: you and I) experienced a while back, and that Brad Wood helped me lock down to a decent repro case. I blog about this current example - with links to various bugs and older blog posts - here: http://adamcameroncoldfusion.blogspot.co.uk/2013/02/another-serious-struct-literal-syntax.html

It's more serious (well: less of an edge-case, anyhow) than this example makes it look.

--

Adam

Thanks duncancumming.

I just found a workaround for that issue. That is if I don't use the argument name, the problem go away...

<cfscript>

          test = {firstName="Bob in line 2"};

          i = 1;

          transaction

          {

                    new mycfc().set("hello", "Bob in text");

                    i++;

                    new mycfc().set("hello", "Bob in text again");

                    new mycfc().set("hello", test);

                    new mycfc().set("hello", {firstName="Bob in line 9"});

                    test2 = {firstName="Merry"};

                    writeDump(var=test2, label="line 11");

                    new mycfc().set("hello", {firstName="Jenny"});

                    i++;

                    new mycfc().set("hello", {firstName="Jenny 2"});

          }

          writeDump("i = #i#");

</cfscript>

You shouldn't use the colon to separate argument name=value pairs.  It's undocumented, use = instead

     new mycfc().set(Text1:"hello",something:"Bob in text");

should be

     new mycfc().set(Text1 = "hello",something = "Bob in text");

Apart from that I couldn't say for the other strangeness you're experiencing.  I've seen problems using inline structures being passed as arguments, try creating them as variables and passing those instead