C#

devvvy wrote:

THUS FAR there isn't ONE SINGLE argument that justify against use of
Thread.Sleep against SCENARIO 2.

Pete O'Hanlon wrote:

Errm. Yes, we have posted arguments against, you're just choosing to ignore them.

devvvy wrote:

1. As I pointed out earlier, there's no need to know *exact* when the blocked thread wakes up again.

Pete O'Hanlon wrote:

There is if you're trying to shut down an application. I don't know how many times I can point out the same thing; perhaps with a simple example - you have a service with a thread that needs to clean up before the service can shut down - by having to wait for the thread to finish, you could trigger the "Service could not be stopped, blah blah blah" message.

<br />
static void Main(string[] args)<br />
        {<br />
            Thread t = new Thread(new ThreadStart(ThreadFunc));<br />
            t.Start();<br />
<br />
            Console.WriteLine("Hit any key to exit.");<br />
            Console.ReadLine();<br />
<br />
            Console.WriteLine("App exiting");<br />
            return;<br />
        }<br />
<br />
        static void ThreadFunc()<br />
        {<br />
            int i=0;<br />
            try<br />
            {<br />
                while (true)<br />
                {<br />
                    Console.WriteLine(i);<br />
                    Thread.Sleep(1000 * 10);<br />
                    i++;<br />
                }<br />
            }<br />
            finally<br />
            {<br />
                Console.WriteLine("Exiting while loop");<br />
            }<br />
            return;<br />

devvvy wrote:

THUS FAR there isn't ONE SINGLE argument that justify against use of Thread.Sleep against SCENARIO 2.

public class Utility
{
  private static readonly object SyncLock = new object();

  public void WaitForTime(int milliseconds)
  {
    lock (SyncLock)
    {
      Monitor.Wait(SyncLock, milliseconds);
    }
  }

  public WakeAllThreads()
  {
    lock (SyncLock)
    {
      Monitor.PulseAll(SyncLock);
    }
  }
}

devvvy wrote:

why the appreciation? It's more code than a simple while loop with a Sleep.

new Utility().WaitForTime(5000);

devvvy wrote:

But this detracts the discussion to get to the bottom