Re: Language module support added

Adriaan de Groot <adridg-FlD2LfDziEhmR6Xm/[email protected]>
Newsgroups gmane.comp.tools.aap.devel
Message-ID <[email protected]>
On Thursday 25 September 2003 21:40, Bram Moolenaar wrote:
> - The ":import" command searches various "modules" directories for a
>   module.  All found modules are loaded in the same scope.  The modules
>   must take care of not defining things that have already been done by
>   checking for the did_import_<name> variable.

OK. The collision in namespace between module names and variables is a pain, 
though, since it means thinking up some contorted module name for the libtool 
module (libtoolmod is what i've settled on, since it's not a language module 
which should be named *lang). In addition, having to do the did_import_ thing 
manually in the module itself feels rather silly .. since it's obvious AAP 
_could_ set that variable itself.

Is there any situation you can think of where multiple module imports would be 
useful?

Anyway, I'm mucking about with the libtool and kde modules again, I'll let you 
know.

-- 
pub  1024D/FEA2A3FE 2002-06-18 Adriaan de Groot <[email protected]>
            If the door is ajar, can we fill it with door-jamb?



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.