X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
Date: Sun, 11 Jan 2009 17:13:49 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: find assert
Message-ID: <20090111161349.GK400@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <495A4B87.3080009@partners.org> <20081230170638.GB5230@ednor.casa.cgf.cx> <20081230174104.GD5230@ednor.casa.cgf.cx> <20081230175246.GE5230@ednor.casa.cgf.cx> <20081230190603.GA13443@ednor.casa.cgf.cx> <49695A74.1010302@byu.net> <20090111091638.GH400@calimero.vinschen.de> <496A0673.108@byu.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@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.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/

