From owner-freebsd-questions Mon Dec 30 12:28:14 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA16484 for questions-outgoing; Mon, 30 Dec 1996 12:28:14 -0800 (PST) Received: from jump.net (serv1-2.jump.net [204.238.120.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA16475 for ; Mon, 30 Dec 1996 12:28:07 -0800 (PST) Received: by jump.net (8.8.4/BERK-6.8.11) id OAA05484; Mon, 30 Dec 1996 14:27:43 -0600 (CST) Date: Mon, 30 Dec 1996 14:27:43 -0600 (CST) From: Lee Crites To: Wes Peters cc: questions@freebsd.org Subject: Re: IPC API's In-Reply-To: <199612290500.WAA08836@obie.softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 28 Dec 1996, Wes Peters wrote: > Has anyone out there ever wrapped a class around these so they're a > little more usable? The SYSV IPC mechanisms are pretty powerful, but > the semaphores and message queues have an *awful* interface. > > Hmmm... a nice little weekend (or two) project in C++ class > construction. Any takers? (I.e. I don't want to do it myself; call > me lazy.) I have all three -- but for aix. I'm in the process of bringing up my FreeBSD box. As soon as I get a few (major) problems worked out, I plan on moving all of my c++ stuff to it an make it work there. I have a class which maintains message sueues, a class which maintains semaphores, a shared memory class, and a socket class. When they are up, I will post them on my home page. I also plan on getting some of my stuff working with pthreads. Ive read some messages about how they work with FreeBSD, but since I don't have my stuff loaded on as of yet, I haven't been abot to test them. Lee