X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Fri, 28 Nov 2008 10:25:56 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: sem_unlink? Message-ID: <20081128092556.GB12905@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20081127231651 DOT GB6403 AT const DOT famille DOT thibault DOT fr> <20081128021823 DOT GG16768 AT ednor DOT casa DOT cgf DOT cx> <20081128090927 DOT GC5154 AT const DOT bordeaux DOT inria DOT fr> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20081128090927.GC5154@const.bordeaux.inria.fr> User-Agent: Mutt/1.5.16 (2007-06-09) 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 Nov 28 10:09, Samuel Thibault wrote: > Christopher Faylor, le Thu 27 Nov 2008 21:18:23 -0500, a écrit : > > On Fri, Nov 28, 2008 at 12:16:51AM +0100, Samuel Thibault wrote: > > >There is no sem_unlink function, is there a reason or is that a PTW? > > > > PTC. It's not easy to get right in a Windows environment. If I read > > what's required correctly it could require interprocess communication. > > Mmm, I haven't tested (and can't right now), but does that mean that > even if sem_open() is currently provided, it does not work? The POSIX semaphore implementation is incomplete in terms of named semaphores up to Cygwin 1.5.25. Cygwin 1.7.0 provides all functions, including sem_unlink. 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/