1. Globals (was: Bug in 1.5a ?)
At 05:52 PM 2/7/98 -0500, you wrote:
>Apparently a lot of people have been severely confused
>by the "global" keyword in Euphoria.
<snip explanation>
Thanks, Robert. That was a very clear explanation of the concept,
which as you state is handled correctly in Euphoria, as opposed to
C <gak><gak>
I had no problem with the idea, but then I haven't programmed in
Basic for about 20 years. (Think that is enough recovery time?)
Irv
----------------------------------------------------------------------------
-----------
Congress is good at two things:
Passing laws, and passing gas.
They put numbers on the laws so we can tell the difference.
----------------------------------------------------------------------------
-----------
2. Re: Globals (was: Bug in 1.5a ?)
- Posted by Arthur Adamson <euclid at ISOC.NET>
Feb 08, 1998
-
Last edited Feb 09, 1998
>>Apparently a lot of people have been severely confused
>>by the "global" keyword in Euphoria.
>Thanks, Robert. That was a very clear explanation of the concept,
>which as you state is handled correctly in Euphoria, as opposed to
>C <gak><gak>
>I had no problem with the idea, but then I haven't programmed in
>Basic for about 20 years. (Think that is enough recovery time?)
>
>Irv
Robert
I would add one item. Robert correct me if I am wrong. The global
vars in a .e file are available to whoever includes the .e file...and they
retain their values while the prog runs.
But..even better, non-global vars declared outside of a procedure or
function in a .e file also retain their values while the program runs. These
vars are available to hold values unavailable directly to other files but
still able to retain internal-to-the-.e-file-values while the prog runs.
They provide the means for some object-oriented-language like behavior.
Bye
Art Adamson
Arthur P. Adamson, The Engine Man, euclid at isoc.net
