Re: (call-process ...) to return correct exit-status on NT
At 10:42 PM 10/15/99 +0200, Adrian Aichner wrote:
>>>>> "Jonathan" == Jonathan Harris
<jhar(a)tardis.ed.ac.uk> writes:
Jonathan> How about using WaitForSingleObject(pid, 1/10s) instead
Hi Jonathan, Craig, All!
Could someone who knows please confirm whether WaitForSingleObject()
will work on Windows9[58]?
The book that I have ("Win32 System Programming" by Johnson M. Hart)
indicates that WaitForSingleObject() works for NT/95/98. (I don't do any
windows programming so I can't answer from personal experience.)
According to MSDN I have to OpenProcess() with SYNCHRONIZE right on
WindowsNT. Windows9[58] does not seem to have this access right. So
I guess I have to open without it there.
This book does not identify SYNCHRONIZE as an NT only option so it should
work with 95/98.
I'll send a patch in a jiffy and would be thankful for a quick
verification by anyone (Craig being to most likely value for
`anyone':-) ) on Windows95 and/or Windows98.
Thanks in advance,
Adrian
Jonathan> of GetExitCodeProcess() in your do...while loop in
Jonathan> wait_for_termination(). That might make XEmacs to use a
Jonathan> lot less CPU and let its child process exit more
Jonathan> quickly. You'll obviously still need to call
Jonathan> GetExitCodeProcess() once after the child has really
Jonathan> terminated.