X-Sybari-Trust: a66fe429 9ffcebbb c096fb41 00000138
From: Martin Stromberg <eplmst AT epl DOT ericsson DOT se>
Message-Id: <200301241426.PAA07035@lws256.lu.erisoft.se>
Subject: Re: _creatnew again [Was: Re: redirection problem with perl]
To: djgpp-workers AT delorie DOT com
Date: Fri, 24 Jan 2003 15:26:36 +0100 (MET)
In-Reply-To: <3E3142BD.F9B0E165@phekda.freeserve.co.uk> from "Richard Dawe" at Jan 24, 2003 01:42:21 PM
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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

> It seems that the extended open-create call has two distinct functions:
> 
> (1) Create and open the file in whatever mode you specify.
> (2) Set the attributes to whatever you specify.
> 
> It seems like (1) controls access through the returned descriptor and (2)
> controls subsequent access to the file (e.g.: after you've closed the
> descriptor).
>  
> So it's possibly to open a file for read-write, but set the file's attributes
> to read-write. You can also create file & simultaneously open it for
     ^^^^^^^^^^ read-only?

> read-only/read-write/write-only and have it read-only subsequently (on disk).

That's weird functionality!

From where does _creatnew() come from? I. e. with what are we
supposedly compatible?


Right,

						MartinS