It is a common mistake to write a textbox like <<textbox $name "default">> where in fact, the author meant to write <<textbox "$name" "default">> so as to have the value stored in the variable $name.
Yet, this cannot simply be errored upon, because it isn't uncommon for users to do something like:
(especially in things like widgets, where you will be accepting a receiver yourself!)
But, for users where this isn't something that they want to do, it could be beneficial to be able to know that they'll avoid mistyping and using a variable directly rather than a string version of it.
Theoretically, this way of writing textbox seems to work: <<textbox '$target' "default">> (assume the single quotes are tilde, for the expression syntax), and so the warning could encourage the user to write out variables which hold references (like $target) with the expression syntax instead. Not perfect, but if it was an optional warning, then that would give an out for those who want to avoid the potential common bug while still using the feature.
It is a common mistake to write a textbox like
<<textbox $name "default">>where in fact, the author meant to write<<textbox "$name" "default">>so as to have the value stored in the variable$name.Yet, this cannot simply be errored upon, because it isn't uncommon for users to do something like:
(especially in things like widgets, where you will be accepting a receiver yourself!)
But, for users where this isn't something that they want to do, it could be beneficial to be able to know that they'll avoid mistyping and using a variable directly rather than a string version of it.
Theoretically, this way of writing
textboxseems to work:<<textbox '$target' "default">>(assume the single quotes are tilde, for the expression syntax), and so the warning could encourage the user to write out variables which hold references (like$target) with the expression syntax instead. Not perfect, but if it was an optional warning, then that would give an out for those who want to avoid the potential common bug while still using the feature.