Re: Scope of globals, parents and children, "load script" and all that jazz
Re: Scope of globals, parents and children, "load script" and all that jazz
- Subject: Re: Scope of globals, parents and children, "load script" and all that jazz
- From: Victor Yee <email@hidden>
- Date: Sun, 20 May 2001 10:38:54 -0400
On Sun, 20 May 2001 16:00:35 +0200, Sander Tekelenburg wrote,
>
> For one thing, a loaded script object doesn't seem to recognise its own
>
> handlers (although it will recognise its own script objects). That
>
> means that you can't have one handler in the loaded object call another
>
> handler within that same loaded object unless they're both wrapped
>
> within a script object declaration within that loaded object (whew, I
>
> just confused myself).
>
>
I think I understand what you're saying, but it doesn't seem to be true. My
>
child script looks like this:
>
[...]
>
>
So the first handler (which doesn't contains any globals) calls the second
>
handler. No problem. Or are you saying that declaring all those variables as
>
globals everywhere turns the handlers into objects?
Whoops! Sorry, I was thnking of script servers. You're right, it does work properly, regardless of the globals.
Now I remember why sleep is a good thing...
:-(
Victor