X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=D/ysA1JppKFwFuRqAcYKuhdw1gCnAtw0hbilqr6SnjX
	lQu12y7zMNjC4txcLU5fp2u1x3AeebegfrKxzd6uZ0T7wiII7YtJFHJOqGrIK5Nj
	E3S3qAyR1k7IOg5cMeflQTACu98jLiyaJNlo4O04WYYUnu1y+96eTzvL/CUgZaX4
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=C0xjnkQXoRpJLAqL0UtKOi/sHLk=; b=KkH5ePbqcZWm6ZOQl
	RHE9vde/649C/H6y1Mp9gAQznCQppIbgMnPNRYOG+q1VmXpMPbf35+qTpIgUIcA9
	j6Ocaun0fqbPGBjPrxTDQe6+khl1YfBCP9X1DibmZZ/1xdDPb4ujzegMDD6z3Ya1
	qKFn5ls0jK1B+Y5BqZzrJbCiPk=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
X-Spam-SWARE-Status: No, score=-4.0 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RP_MATCHES_RCVD autolearn=ham version=3.3.1
Message-ID: <51AF7303.8060303@etr-usa.com>
Date: Wed, 05 Jun 2013 11:18:59 -0600
From: Warren Young <warren AT etr-usa DOT com>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Mandatory file locking semantics
References: <51A7862F DOT 1070507 AT etr-usa DOT com> <51A7D47E DOT 3050502 AT users DOT sourceforge DOT net> <51A7F547 DOT 6020509 AT etr-usa DOT com> <20130531092228 DOT GB30659 AT calimero DOT vinschen DOT de> <51A900EF DOT 2020606 AT etr-usa DOT com> <20130601105741 DOT GC30659 AT calimero DOT vinschen DOT de> <20130602103125 DOT GE13934 AT calimero DOT vinschen DOT de> <51ACD415 DOT 2090709 AT etr-usa DOT com> <20130604084815 DOT GD19572 AT calimero DOT vinschen DOT de> <51AF6433 DOT 5050104 AT etr-usa DOT com> <20130605170246 DOT GD3250 AT calimero DOT vinschen DOT de>
In-Reply-To: <20130605170246.GD3250@calimero.vinschen.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 6/5/2013 11:02, Corinna Vinschen wrote:
> The burden to use it correctly is
> on the application developer.

That's always true, for all APIs.

If a design change can make it more likely that application developers 
will use it correctly, shouldn't the design be changed?

It's not like anyone is actually depending on this yet.  Granted, it's 
now present in a release version of Cygwin, but you declared it 
preliminary.  I don't see that anyone can complain if the design changes 
before it's declared stable.

What does the fcntl(F_LCK_MANDATORY) design have to recommend it, other 
than "it already exists"?

Understand, I'm not rejecting your gift to the community.  If this is 
all I can have, I'm glad to have it.  This may be your job, but you 
aren't my employee, so I don't feel any expectation that you should do 
what I want.  I'm just asking nicely.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple