granted, I'm doing a cfscript closure in CFML, but I've done that many many times w/o problems. And it works. Perfectly. In this case. Before the unrelated changes.

And it works. Perfectly. In this case. Before the unrelated changes.

I would not call that "working perfectly" ;-) TBH, as well as defeating the CF parser, the code ain't as readable as it could be with the array mapping inline in the function call. Your second variant is a lot better.

personally I like 1-time-use variables. giving things names communicates what the intent is, where a compact thing may save space, but can be a bit dense to read/maintain easily. our team adopted a "let's avoid variables that only get referenced in one place" policy, so I go along with it (usually bwahaha)

Your team needs a good talking to.