Re: Why doesn't this work? (short)

new topic     » goto parent     » topic index » view thread      » older message » newer message

Hello Dear EU users:

Igor Kachan (me:) wrote

> Dear EU users:
> 
> Just IMHO.
> 
> Just globals must be real globals
> and must be visible anywhere  blink
> 
> EU is simple and clear language,
> please, do not forget about this=20
> simple thing.

I have to explain these thesises more clearly, I think now.
(BTW take a look to a Topica's "this=20", "this=BbUuGg", not 20).

Good programming language MUST be clear.
English key words of EU were absolutelly clear for most 
Russians. Now single exeption relates to the *global* word 
after, so to say, the namespace 'revolution'.

This common word has it's *main* sense, so the action of the 
*global* operator of EU programming language must be 
as close to this sense as possible without many words
to explain what is EU global really.

And this *global* operator may have some additional
features detailed in documentation.

But now, you must first of all learn *these additional features*
to understand common word *global* well in EU and avoid the
cryptic bugs. The OOP concept is difficult for understanding
just because of similar abstractions.

For good and easy understanding, space of the global names
has to be more and more common-single-monolite for the user's
program with all include files after the points of including.
If you need separate that common space because of names 
conflicts -- use additional features, use the AS form of 
the include operator, you may even rename yourself blink

This common-single-monolite space of the global names may
be organized with better warning system, something similar 
to the builtin names, I think. Globals are too important to be
silently ignored or overridden in a program of novice nor guru.
Novice has no experience, guru has no his own memory to remember
all win32lib or Win95/98/ME/2000/X/XP - Linux/DOS32/FreeBSD 
- EU own globals' names blink
"with/without globals" or similar command is not so good
as just warning or aborting, I think.

Remember please, an include file with its include files may 
be just included into your program and then same include 
file may be executed from same your program with system_exec() 
command any times in any points you wish. 
This feature is powerful but rare used for now. 

Sorry, just IMHO again.

Regards,
Igor Kachan
kinz at peterlink.ru

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu