Hi everyone: When I want to design "a plugin for a plugin", I may use such a feature. i.e. a plugin which is a generic framework for a kind of engine plugins, which could be implemented by another script:
plugin/framework.vim engine_a.vim engine_b.vim engine_c.vim there may be different engines, we can only enable one of them at each vim session, the framework will call engine's initialization and some interface functions, inside the engine.vim script it may need to set some s:variables and access some s:functions inside framework.vim This architecture requires the framework give the access right of some variables and functions to the engine. If we define g: variables it will be global, I want the engine to be the "friend" of the framework, i.e. the particular script engine.vim can access all script-local stuffs of framework.vim, is that possible? Or is it possible for two scripts sharing the same script-local namespace? --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
