The Dink Network

Reply to Re: Why Can't I Quit You, DinkC?

If you don't have an account, just leave the password field blank.
Username:
Password:
Subject:
Antispam: Enter Dink Smallwood's last name (surname) below.
Formatting: :) :( ;( :P ;) :D >( : :s :O evil cat blood
Bold font Italic font hyperlink Code tags
Message:
 
 
November 5th 2013, 08:06 PM
peasantm.gif
shevek
Peasant They/Them Netherlands
Never be afraid to ask, but don't demand an answer 
Perhaps I understood you incorrectly?

It seems so.

I meant that the point from where the spawned script was called will be ignored.

I meant the fact that the spawned script returned would be ignored.

When the spawned script returns, nothing happens.

That's what I meant. But it's not true, according to your test: the calling script will stop waiting, which is quite different from "nothing". Even if it is by now waiting for something completely different, it still stops waiting.

Most of the time, the event that interrupted the call will have completed, and it is waiting for the next event. In that case, it can't really continue, so it will immediately start waiting again. But if it was waiting for a wait() (and I'm guessing also a say_stop or move_stop), the waiting is aborted and the script immediately continues. If the returning of the spawned script would be ignored, it would have no influence on this waiting (or on anything else, of course). So I conclude that it is not ignored.