SRL Archive - Jr. Member General Help and Discussion

Is there a difference between the functions :

wait(100);

and

sleep(100);

If so, what are the differences?

I'm now actually also interested in the answer to this!

I've wondered about this too. Maybe someone can actually explain it but here is what a quick search turned up

1.“Sleep” is a thread management method that is defined as a static method while “wait” is a thread management method which is defined in the Object class.
2.Sleep is a method that executes threads while wait is a method that executes objects.
3.Sleep keeps the synchronization locks of the current thread and influences the behavior of applications while wait does not.
4.Sleep controls the execution of the thread and does not allow other threads in a synchronized block while wait does not control the execution of the thread to let other threads run.

source:
http://www.differencebetween.net/technology/software-technology/difference-between-sleep-and-wait/

From: evilcitrus
…

Seems more relevant to multithreading then, which scripts don't support yet, unless this means the script running thread versus for example the extensions, and other stuff going on in Simba. A dev answer would be awesome, I'm curious too.

Well I went searching on the GIT.. this is what I found

procedure Sleep(milliseconds: Cardinal);
begin
{$IFDEF MSWINDOWS}
  {$IFDEF FPC}
  sysutils.sleep(milliseconds);
  {$ELSE}
  windows.sleep(milliseconds);
  {$ENDIF}
{$ELSE}
  sysutils.sleep(milliseconds);
{$ENDIF}

end;

https://github.com/MerlijnWajer/Simba/blob/1327b37c83a99d14279c25fd610b134bbcadba39/Units/Synapse/synafpc.pas

It's exactly the same… Wait just calls sleep iirc. If you want to know why its there ask who added Wait to scar.

From: Olly
It's exactly the same… Wait just calls sleep iirc. If you want to know why its there ask who added Wait to scar.

yup.

procedure ps_Wait(t: DWord); extdecl;
{$ifdef MSWINDOWS}
begin
  Sleep(t);
end;
{$else}
var
  EndTime : DWord;
begin
  if t > 50 then
  begin;
    EndTime := GetTickCount + t;
    while {(CurrThread.PSScript.Exec.Status = isRunning) and }(GetTickCount < EndTime) do
      Sleep(16);
  end else
  begin
    sleep(t);
  end;
end;
{$endif}

https://github.com/MerlijnWajer/Simba/blob/1327b37c83a99d14279c25fd610b134bbcadba39/Units/MMLAddon/PSInc/Wrappers/other.inc#L40

So we are clear, lape_Wait() calls ps_Wait() (the proc above).

it's native (sleep) and the clock cycle ms is important in sleep.
so always use wait, and not have the added consequence in sleep, but basically have all the benefits of sleep.

From: Olly
It's exactly the same… Wait just calls sleep iirc. If you want to know why its there ask who added Wait to scar.

Probably because the name sleep refers to setting a thread in sleep mode. Most starting script writers don't know what a thread is, thus the name wait fits that function way better. But that is just an opinion of course.

From: Turpinator
yup.

procedure ps_Wait(t: DWord); extdecl;
{$ifdef MSWINDOWS}
begin
  Sleep(t);
end;
{$else}
var
  EndTime : DWord;
begin
  if t > 50 then
  begin;
    EndTime := GetTickCount + t;
    while {(CurrThread.PSScript.Exec.Status = isRunning) and }(GetTickCount < EndTime) do
      Sleep(16);
  end else
  begin
    sleep(t);
  end;
end;
{$endif}

https://github.com/MerlijnWajer/Simba/blob/1327b37c83a99d14279c25fd610b134bbcadba39/Units/MMLAddon/PSInc/Wrappers/other.inc#L40

So we are clear, lape_Wait() calls ps_Wait() (the proc above).

Looks like it was written to catch script/thread exits on linux.

Since that was commented, it's pointless and wasting cpu.