Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Wed, 28 Mar 2001 16:36:42 -0500 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com, cygwin-developers AT cygwin DOT com Subject: Re: PostgreSQL and cygipc Message-ID: <20010328163642.A2091@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com, cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com, cygwin-developers AT cygwin DOT com References: <20010328103531 DOT C465 AT dothill DOT com> <20010328105608 DOT C32159 AT redhat DOT com> <3AC2520E DOT 96D89DC8 AT ece DOT gatech DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <3AC2520E.96D89DC8@ece.gatech.edu>; from cwilson@ece.gatech.edu on Wed, Mar 28, 2001 at 04:05:18PM -0500 On Wed, Mar 28, 2001 at 04:05:18PM -0500, Charles Wilson wrote: >Worse, the existence of the cygipc library as a standard component will >dis-incentive folks to develop a working substitute that CAN be added to >the cygwin dll. > >Do we *really* want to include cygipc in "contrib"? Good point. I seem to have a little bit of deja vu seeing these. I wonder if I have made the same points myself. Now that you mention this, I've always resisted looking at the cygipc code in case I wanted to do my own implementation someday. I did download an os/2 version of an IPC library that was public domain a while ago, though. After poking at it for a while, I came to the conclusion that I could do a better job. Of course, that meant that I didn't really do any job. :-) I did implement the semaphore part of the IPC stuff in a rudimentary fashion a few years ago, though. I could donate that code to anyone who was interested in working on this.