search for: shouldshowstatus

...Reid Spencer <reid at x10sys.com> >Date: Fri, 24 Sep 2004 13:03:44 -0700 > >I just discovered that the *only* place this is used is in the debugger >when it is loading files, etc. There should be a way to do this without an >alarm. In fact, a thread could easily set the "ShouldShowStatus" every >second until the the thing is cancelled. Since the caller is required to >update the progress, this could also be done with time deltas without the >use of threads or signals. When I get the lib/System/TimeValue abstraction >implemented, I'll probably just update Sl...

...d at x10sys.com> >>Date: Fri, 24 Sep 2004 13:03:44 -0700 >> >>I just discovered that the *only* place this is used is in the debugger >>when it is loading files, etc. There should be a way to do this without an >>alarm. In fact, a thread could easily set the "ShouldShowStatus" every >>second until the the thing is cancelled. Since the caller is required to >>update the progress, this could also be done with time deltas without the >>use of threads or signals. When I get the lib/System/TimeValue abstraction >>implemented, I'll probabl...

There's simply no equivalent to signals on Windows. There is no way to asynchronously interrupt a thread's processing to execute some handler. The only thing you can asynchronously do to a thread is kill it, and that's generally frowned upon (who knows what critical sections it might be holding, etc...). Stuff like alarms is supposed to be done using the "event-driven"

Ultimately, this is another function that needs to go into lib/System. An alternate approach is to fork a thread, sleep, and when the thread wakes up, "ring the alarm". Reid. John Criswell wrote: > Henrik Bach wrote: > >> Hi >> >> I'm compiling: >> /usr/local/src/llvm/lib/Support/SlowOperationInformer.cpp on MinGW. >> However, it stops