Article View: comp.windows.ms.programmer
Article #2061Re: Windows, Exec, Subprogram
From: Isaac Rabinovitch
Date: Fri, 12 Apr 1991 21:16
Date: Fri, 12 Apr 1991 21:16
25 lines
1234 bytes
1234 bytes
In <1266500005@cdp> jeff@cdp.UUCP writes:
>By the way, note that WinExec() is asynchronous, and will probably
>return before the requested program has completed.
> Jeff Dean
Which reminds me of a problem that's been bothering me since I first
started playing with windows: when you WinExec() or LoadModule() a
program, how to you find out the handle of the window you've just
created?
Here's another one: what's the practical difference between WinExec()
and LoadModule(). Please don't say "WinExec is an alternative to
LoadModule() and vice versa" -- only lazy techwriters are allowed to
do things like that!
--
ergo@netcom.com Isaac Rabinovitch
netcom!ergo@apple.com Silicon Valley, CA
{apple,amdahl,claris}!netcom!ergo
All work and no play makes Jack a dull boy. -- Jack
Technical Details
Message-ID:
<1991Apr12.211658.28611@netcom.COM>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!apple!netcom!ergoReferences:
<1997375683@1991Apr10.170742.799@bellcore.be> <1266500005@cdp>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!apple!netcom!ergo From: ergo@netcom.COM (Isaac Rabinovitch) Newsgroups: comp.windows.ms.programmer Subject: Re: Windows, Exec, Subprogram Message-ID: <1991Apr12.211658.28611@netcom.COM> Date: 12 Apr 91 21:16:58 GMT References: <1997375683@1991Apr10.170742.799@bellcore.be> <1266500005@cdp> Organization: UESPA Lines: 25