X-Authentication-Warning:	acp3bf.physik.rwth-aachen.de: broeker owned process doing -bs
Date:	Wed, 14 Jun 2000 15:58:01 +0200 (MET DST)
From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
X-Sender:	broeker AT acp3bf
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc:	djgpp AT delorie DOT com
Subject:	Re: PBM Utilities
In-Reply-To:	<Pine.SUN.3.91.1000614164334.995A-100000@is>
Message-ID:	<Pine.LNX.4.10.10006141553060.6658-100000@acp3bf>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Wed, 14 Jun 2000, Eli Zaretskii wrote:
> On Wed, 14 Jun 2000, Hans-Bernhard Broeker wrote:

> > There's also the additional complication that most PBM
> > utilities need their stdout and stdin in binary mode. I'm not sure 
> > the command/c method preserves this across the '|', off hand.
> 
> I'm afraid I don't follow.  First, the binary mode is something that only 
> exists at the application level; DOS itself doesn't know anything about 
> it (it's the library which implements the distinction).  

Well, it's DOS's command.com emulating the '|' by a temporary file. And
there are three instances of command.com participating in a command line
like

	command /c bat1.bat | command /c bat2.bat

(the one running the prompt, and the two explicitly started)

> If that's what happens, I don't see why do you need to
> worry about peserving the binary mode across applications.

I don't _know_ I need to. But neither am I sure I don't. I'd have to
experiment, but I don't have a DOS system at hand.

Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -