Date: Tue, 13 Jun 2000 11:47:13 -0400
Message-Id: <200006131547.LAA06047@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp-workers AT delorie DOT com
In-reply-to: <200006131530.LAA10059@qnx.com> (alain@qnx.com)
Subject: Re: tmpfile in DJGPP
References:  <200006131530 DOT LAA10059 AT qnx DOT com>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> > trick Bash (and other Unix programs) use is inherently non-portable,
> 
> Well Eli, I think I have to disagree, non-portable according to what ?

Non-portable to other OS's besides POSIX ones.  POSIX is *not* the
only game in town.

> > so I think it's a good idea to remove it even on Unix.
> 
> open()/unlink()/close() are very well documented in POSIX.

It doesn't matter.  The fact that we're running on top of a DOS-type
file system limits the amount of posix compliance we can offer.  Note
that POSIX also says that text files are \n, not \r\n, even though
ANSI says you can't assume that.  DJGPP offers as much POSIX
compatibility as possible, given the limitations of DOS, but
programmers still have to be aware of the porting issues.