OpenEuphoria

2. Re: Phix: How to Globalize(?) a Namespace Identifier

• Posted by petelomax May 28, 2020
• 1826 views

No.

The idea that someone/anyone would want to use mgr: in primary_app.exw without declaring mgr totally complexes me, and always has. When I see mgr: and the source file does not tell me where I should look, well that's just plain rude.

The use of "namespace helpers" in helpers.e so you do not have to say "as helpers" on the include likewise befuddles me and has only been added rather reluctantly, and probably has "bugs", one of which will almost certainly bite you if you try to do the first of what I am about to suggest.

Either:

include helpers.e as helpers 
include helpers.e as mgr 

or

include helpers.e as helpers 
include manager.e as mgr 

or

helpers:initiate()   -- [1] 

or

initiate_mgr()  -- [2] 

There are no doubt plenty of other ways, such as using routine_ids.

[1]: Uses the include-tree to resolve, assumes that helpers.e does not also contain/include skivvies:initiate()
[2]: I always have and always will maintain that is the best solution. As a bonus a simple search gets exactly what I want, rather than a list of two dozen or more to pick from.

PS: The whole point of namespaces is to resolve clashing globals. If you allow namespaces to be global then by rights you would also have to invent an entirely new mechanism to resolve clashing global namespaces.
Suppose John ships his helpful utilities library with util:init().
And then Jim also ships a library with util:init().
With "include as" being the place where util is defined, the solution for using both is trivial.
With "namespace util" in both you would require a sub-include mechanism to avoid the conflict, but it is doable.
With "global namespace util" you would have no option but to modify their sources every time they issued a new version.

4. Re: Phix: How to Globalize(?) a Namespace Identifier

• Posted by euphoric (admin) May 28, 2020
• 1830 views

That's a good point, and I was probably going overboard on my attempt to make more modular my code scaffold.

In my primary app, I was including this helper app which included other modules that my primary app would need. These other modules are all namespaced with "as ..."

I'll probably just move those includes back into the primary source. It just means that I cannot use an include file that includes other modules.

If I do this:

-- mods.e 
public include helper.e as help 

then the "help" namespace should propagate to any parent source... no?

include mods.e 
help:package() 

or (?)

public include mods.e 
help:package() 

6. Re: Phix: How to Globalize(?) a Namespace Identifier

• Posted by petelomax May 31, 2020
• 1792 views

Hah! I particularly enjoyed my own conspicuous absence from all that particularly vacuous nonsense!

I have always been in the ftp_open() is better than ftp:open() camp, and recall 3 or 4 years ago being slightly apprehensive over banning builtin overrides in Phix, but in all the time since, doing so has not bitten me back even once.