iRules Style Guide

Great article. Most things are cosmetical, but some realy important things are mentioned also. I will highlight:

• K15650046: Tcl code injection security exposure
• Always wrap expressions in curly brackets to avoid double expansion
• iRule priorities
• the static:: behavior

I see in in the wild often scripts that violates against these best practices.

What also could be mentioned is: switch cases do not need any "return" or "break" statements, too not fall through. I saw "return" many times errorneous used in this context.