Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Wed, 10 Apr 2002 15:35:46 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: REPOST: unlink semantics Message-ID: <20020410153546.N1127@cygbert.vinschen.de> Mail-Followup-To: cygwin@cygwin.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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@cygwin.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/