unused var, but it is used.

[KrunchMuffin]

so it seems if I do something like this

var foo = "";
transaction {
    foo = 1; 
    ...other stuff...
}

I get a cflint error saying foo is unused. If I put it inside the transaction error goes away.
I don't know if this is a bug or actually a real case scenario. Never heard that variables made outside a transaction are not available inside a transaction, but maybe it is the case.
Anyone know for sure?

[ryaneberly]

cflint is not making a statement about the nature of transactions and variables. I think this is a CFLint false positive bug.

[KamasamaK]

As I understand the rule, assignment does not constitute usage, so I would expect it to also report within the transaction as presented. I'm not sure I would call the issue a false positive without seeing the case where it reports.

[KrunchMuffin]

here u go

[KamasamaK]

So because it is returned, it should definitely be seen as used.

Regardless, I am still confused. You said when it's put inside the transaction error goes away, but you are also saying that it is reporting it here where it is in a transaction. What exactly makes the error go away?

[KrunchMuffin]

No, if I set the var inside the transaction it goes away, didn't make that very clear, in original post, sorry.

[KamasamaK]

I see. When it's declared in the transaction block then it's fine. Thanks for clarifying.

[ryaneberly]

hmm, first while blocks, and now transaction blocks. Both were being skipped by cflint. I believe any others should be resolved in a generic fashion now.

This is fixed in dev branch, will be available in 1.3.0