Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Wed, 10 Apr 2002 15:35:46 +0200
From: Corinna Vinschen <cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: REPOST: unlink semantics
Message-ID: <20020410153546.N1127@cygbert.vinschen.de>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <FC169E059D1A0442A04C40F86D9BA76008ACAC AT itdomain003 DOT itdomain DOT net DOT au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <FC169E059D1A0442A04C40F86D9BA76008ACAC@itdomain003.itdomain.net.au>
User-Agent: Mutt/1.3.22.1i

On Wed, Apr 10, 2002 at 10:20:04PM +1000, Robert Collins wrote:
> > As a suggested fix, path_conv::check could 
> > returns ENOENT for a file if it appears in the delqueue. 
> 
> This introduces it's own problems: what happens when the application
> then tries to create a new file with that file name? Do we give it a
> random temporary name? What happens when the app then calls a non-cygwin
> program with the file name.... oops!

Yes, you can't make everyone happy.  The Windows semantics when
deleting a file in use is so different from POSIX, that you will
always find a situation which won't work as in POSIX.  Regardless
of the effort you make to "get it right".

I don't think it's worth it.  The whole delqueue approach is just
a crook and will always be.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/