Re: Namespace Proposal
Dear Eu users,
Just my point of view.
If there is no conflict, there is no any problem. No ?
So, *interpreter* must see on situation, only if there
*is* the **concrete** conflict in the ***new*** program.
Suppose, I use library1.e and library2.e
-------prog1.ex
include library1.e
include library2.e
integer My
My=1
-------end prog1.ex
Run prog1.ex under Eu 2.3 control
See warning message:
"Symbol My is defined as global in library1.e, rename yours new one
or use that old one as a.My"
"Symbol My is defined as global in library2.e, rename yours new one
or use that old one as b.My"
You can choice, rename new variable or use the old good symbol under
recommended simplest syntax.
Explanation of the notation char.My is very clear
a -- this is the first conflict of My symbols in the *new* program and in
library1.e
b -- this is the second conflict of My symbols in the *new* program and in
library2.e
c -- this is the next and so on.
I don't know, maybe this variant is well known and
an old one, but I like it.
I don't like the *superglobal* variant of automated
main-fail priority.
Global is global. No ?
Regards,
Igor Kachan
kinz at peterlink.ru
|
Not Categorized, Please Help
|
|