Date: Thu, 13 Jul 2000 16:08:21 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Olaf van der Spek <Olaf AT XCC DOT TMFWeb DOT NL>
cc: djgpp AT delorie DOT com
Subject: Re: Pipe to sendmail (again)
In-Reply-To: <qXgb5.371305$k22.1589483@flipper>
Message-ID: <Pine.SUN.3.91.1000713160629.14968A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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
Precedence: bulk


On Thu, 13 Jul 2000, Olaf van der Spek wrote:

> > Absence of 'b' means *default*, which can still be binary if you (or
> > the application, if you are a library) have set the _fmode variable
> > appropriately.
> >
> > In cygwin, the "default" comes from the mount table, and is often
> > "binary", so the "t" is a good idea.
> 
> But it caused popen to fail, so it doesn't seem that good to me always.

If "wt" fails, it means that the library you are using is non-ANSI.  ANSI 
C defines the "t" flag and requires a complying library to support it 
(which on Unix means simply to ignore it).

If the C library on your machine is not ANSI-compliant, then you indeed 
should not use "t".