Originally Posted by Cargor
In this case, I would guess that it prints out the empty string (e.g. ""), since Blizz mostly doesn't check beforehand if the string is empty or not. If you set it nil, it would most likely result in an error.
Just try it  |
Set it to nil and disable lua errors!
...
/runawayinshame
Originally Posted by Cargor
There are also examples where global strings are used in a secure environment and if you change them, they become tainted and can block code from functioning correctly.
A good example is the global string RANGE_INDICATOR (which is the small dot on action bars and the item-button of the quest tracker) - if you set it to "" to hide it, the item-button doesn't work anymore if you click it, because its environment is tainted.
|
Nice to know. I wouldn't have guessed that global strings could be used in any secure environment. Not that there's any problem with not being able to change RANGE_INDICATOR though