X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Sun, 11 Jan 2009 17:13:49 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: find assert Message-ID: <20090111161349.GK400@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <495A4B87 DOT 3080009 AT partners DOT org> <20081230170638 DOT GB5230 AT ednor DOT casa DOT cgf DOT cx> <20081230174104 DOT GD5230 AT ednor DOT casa DOT cgf DOT cx> <20081230175246 DOT GE5230 AT ednor DOT casa DOT cgf DOT cx> <20081230190603 DOT GA13443 AT ednor DOT casa DOT cgf DOT cx> <49695A74 DOT 1010302 AT byu DOT net> <20090111091638 DOT GH400 AT calimero DOT vinschen DOT de> <496A0673 DOT 108 AT byu DOT net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <496A0673.108@byu.net> User-Agent: Mutt/1.5.17 (2007-11-01) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Jan 11 07:47, Eric Blake wrote: > According to Corinna Vinschen on 1/11/2009 2:16 AM: > > Are you proposing that Cygwin should change setting errno from ENOSHARE > > to ENOENT? ENOSHARE is only set in one single instance and is only > > explicitly requested in another. AFAICS, dropping ENOSHARE entirely > > would only simplify the code and should have no negative consequences > > (knock on wood here). > > Changing from ENOSHARE to ENOENT would certainly be more POSIX-compliant - > the error is conveying the information that a path does not exist. Also, > if you put some historical context on the problem, ENOSHARE predates the > implementation of the // namespace. Back when //server did not represent > a valid path name, it made sense to have a different error for > //nosuch/share seeing as how //nosuch could never resolve on its own. But > now that //nosuch can potentially resolve, it makes sense to treat it like > any other path name that can potentially resolve, by returning ENOENT. That makes sense. I changed ENOSHARE to ENOENT throughout. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/