Change Details

As noted in T214674#5396912, AbuseFilter currently allows declaring variable variables with setter functions, e.g. ``` set_var( page_title + '_my_string' + ( page_namespace == 0 ? 'main' : 'foo' ), 'myVarValue' ) ``` is valid syntax. However, the AF language is meant to be simple, and variable variables are something complicated to deal with even in standard programming languages. So my proposal is to only allow a literal string as first argument to set_var.

As noted in T214674#5396912, AbuseFilter currently allows declaring dynamic variables with setter functions, e.g. ``` set_var( page_title + '_my_string' + ( page_namespace == 0 ? 'main' : 'foo' ), 'myVarValue' ) ``` is valid syntax. However, the AF language is meant to be simple, and dynamic variables are something complicated to deal with even in standard programming languages. So my proposal is to only allow a literal string as first argument to set_var.

As noted in T214674#5396912, AbuseFilter currently allows declaring variabledynamic variables with setter functions, e.g. ``` set_var( page_title + '_my_string' + ( page_namespace == 0 ? 'main' : 'foo' ), 'myVarValue' ) ``` is valid syntax. However, the AF language is meant to be simple, and variabledynamic variables are something complicated to deal with even in standard programming languages. So my proposal is to only allow a literal string as first argument to set_var.