Re: Any info about "Thread has exited with code 32772 (0x8004)"?
- From: Joseph M. Newcomer <newcomer@xxxxxxxxxxxx>
- Date: Thu, 14 Feb 2008 11:21:20 -0500
Duh, what's a "batch file"?
Seriously, one of the great things about using Windows is that I rarely write batch files,
and the only case I still use sets up an environment variable for the awk compiler I have
so the awk runtime can be found (AWKPATH=), and invoking the awk compiler with the long
list of switches and options required. In a reasonable world, this information would be
specified once. Some day I'm going to write a little program that does this for me
automatically, and remembers the settings in the Registry for each project (not this week,
though; after browsing email and newsgroups, it's Tax Prep Time Again...)
One of the things I universally detested about Unix and Unix philosophy was that you could
use scripts to do everything. Scripts and pipes were the answer to every problem. There
was a time when I could tell you about the quoting conventions in three kinds of Unix
shells that were required to make the scripts run at all, and the disaster was that if a
script returned nonzero, all you knew was "something failed" but you had no idea which of
the many steps *actually* failed, and consequently what state the data ended up in. Half
of my scripting code was trying to figure out how to return appropriate error notification
to the caller of the script, and clean up whatever mess the failure left behind.
There was a time in my life when I was really interested in scripting languages of all
sorts, and had even written a few. With Windows, I no longer have to care at all about
them, and I like it that way.
joe
On Wed, 13 Feb 2008 15:03:21 -0800, "Tom Serface" <tom.nospam@xxxxxxxxxxxxx> wrote:
Yikes, someone actually still uses batch files :o) Sorry, hadn't consideredJoseph M. Newcomer [MVP]
that.
Tom
"David Ching" <dc@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:IuKsj.7089$5K1.181@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
"Tom Serface" <tom.nospam@xxxxxxxxxxxxx> wrote in message
news:20A2ED75-2C8C-4A23-84DF-BC1EA0C5A19F@xxxxxxxxxxxxxxxx
Agreed, however with Windows it is often difficult to know what you are
returning "to" or "from" so it's less likely that people will use return
codes and, instead, use some sort of interprocess communication scheme.
Of course, you can wait for objects that you ShellExecuteEx(), but I even
find that to be klunky.
But your GUI app could just as well be invoked from a batch file... which
of course halts until the program returns. This is pretty common,
actually.
-- David
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
.
- Follow-Ups:
- Re: Any info about "Thread has exited with code 32772 (0x8004)"?
- From: David Ching
- Re: Any info about "Thread has exited with code 32772 (0x8004)"?
- References:
- Re: Any info about "Thread has exited with code 32772 (0x8004)"?
- From: Joseph M . Newcomer
- Re: Any info about "Thread has exited with code 32772 (0x8004)"?
- From: David Ching
- Re: Any info about "Thread has exited with code 32772 (0x8004)"?
- From: Joseph M . Newcomer
- Re: Any info about "Thread has exited with code 32772 (0x8004)"?
- From: David Ching
- Re: Any info about "Thread has exited with code 32772 (0x8004)"?
- From: Tom Serface
- Re: Any info about "Thread has exited with code 32772 (0x8004)"?
- From: David Ching
- Re: Any info about "Thread has exited with code 32772 (0x8004)"?
- From: David Ching
- Re: Any info about "Thread has exited with code 32772 (0x8004)"?
- Prev by Date: Re: CString manipulation
- Next by Date: Re: Clearing screen
- Previous by thread: Re: Any info about "Thread has exited with code 32772 (0x8004)"?
- Next by thread: Re: Any info about "Thread has exited with code 32772 (0x8004)"?
- Index(es):
Relevant Pages
|