OpenEuphoria

Re: Namespace clobbering internals

• Posted by Jason Gade <jaygade at yah?o.co?> May 01, 2008
• 756 views

Shawn Pringle wrote:
> 
> I saw the idea of keeping symbols out of the global scope necessary for 
> porting existing EUPHORIA applications and libraries to the new standard
> library.
> Imagine you have 12,000 lines of code and you wish to use this new standard
> 
> library.  Can you imagine having to do a search and replace for every builtin
> 
> to include an eu: namespace qualifier?
> 
> Perhaps it is just better to avoid the names of builtins in the first place
> unless 
> you really want to override them.  Instead of open and close, the same kind
> of
> thing could be called connect() and disconnect().
> 
> Shawn Pringle

But you wouldn't have to do that really (although automation certainly eases the
task). You would only have to add a namespace qualifier to symbols that clashed.

And if a namespace keyword was adopted as has been suggested then I think that
conflicts would be far easier to fix.

--
A complex system that works is invariably found to have evolved from a simple
system that works.
--John Gall's 15th law of Systemantics.

"Premature optimization is the root of all evil in programming."
--C.A.R. Hoare

j.