Upon further reflection about the situation in Rev (as opposed to
languages that are really compiled, and execute from the start of the
program each time a change is made), I take your point. In Pascal, the
program/compiler must re-create each global each time the program is
run. In Rev, the program never actually stops running (in some sense,
even though it does change as the programmer edits the scripts and
modifies the properties), so there is never a time when Rev can properly
re-evaluate the existence of the globals. Removing all of the globals
each time a script is edited would not work.
See: I'm still having problems getting my mind around all of the
implications of a Rev-like IDE...
:)
Jon
Richard Gaskin wrote:
Jon wrote:
I agree: it is unfortunate that the original language designers used
the term "global" to mean "persistent global". Had they separated
the concept of scope from the concept of variable duration/lifetime,
the language would have been equally powerful while being easier to
understand.
What is a non-persistent global?
In any language I've worked with, you declare a global and it stays in
memory until you delete it or quit the program.
I don't know of any language that deletes globals automatically based
on whether the app closes or opens files from disk.
--
Richard Gaskin
Managing Editor, revJournal
_______________________________________________________
Rev tips, tutorials and more: http://www.revJournal.com
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
