> All global variables can be found through g: which is a hash table > itself. It might be good to hide those variable from outside and > limit its use only to the plugin itself.
Users wouldn't be able then to change the value of that variable without restarting vim. I personally don't fully understand why some plugin authors try to encapsule such parameters when they are developing for an interactive environment like vim, which IMHO follows different rules than developing in, e.g., C++. In emacs, all variables are global and users are supposed to tinker with "plugins" and to amend it in whichever way they want to. In smalltalk, IIRC everything is globally accessible either and they do well. I'm not saying that we should make everything global and there are of course use cases where you wouldn't want the value to change during execution once it was set (as if it were defined "final") but I wouldn't expect that to be the case very often. More than once, I gave up on a plugin because its author considered it absolutely necessary to limit plugin configuration by using such a technique. Tom. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
