OpenEuphoria

Re: Universal Namespace Clearinghouse

• Posted by gertie at ad-tek.net Jun 22, 2001
• 387 views

On 23 Jun 2001, at 0:21, Irv Mullins wrote:

<snip>

> The only workable solution is to name the space at the 
> time it is imported, with a name that would be meaningful only within the 
> scope of that one file. If other files also import the same library, they 
> are free to rename it however they wish, and there will be no conflicts.

I believe that is the key to the whole mess, the *local* include name. If you
wish to
make global your local name for a included renamed procedure, you'd just haveto 
make a global procedure of a similar name. Or,,, to pass on the renamed include 
file's functions.....

global include win32lib as win

Kat