Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 From: "Gary R. Van Sickle" To: Subject: RE: OT: possible project/research project Date: Tue, 19 Mar 2002 20:51:53 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <00c501c1cfaf$50e1db50$0200a8c0@sknet01> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal > -----Original Message----- > From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]On Behalf > Of Stephano Mariani > Sent: Tuesday, March 19, 2002 7:34 PM > To: 'Randall R Schulz'; 'Robert Collins'; cygwin AT cygwin DOT com > Subject: RE: OT: possible project/research project > > > I am no cygwin expert, or windows expert, but isn't the effort better > spent getting the cygwin fork/vfork to work faster? > > Stephano Mariani > > PS: Please do not fry me if this is a stupid suggestion or not possible > because of an obvious flaw, I simply fail to see why the source of the > problem is not being targeted. > I don't see it that the source of the problem is the implementation of fork/vfork; the way I see it the very *concept* of forking makes little to no sense. I've written a lot of code, and not once have I thought to myself, "ok, now what I want to do here is duplicate the current process in almost exactly its current state." Maybe it made more sense back in the day, or maybe I'm missing something, but it seems to me there's a lot more efficient ways to do multithreading/multi"process"ing/IPC/etc (or better yet avoid them altogether) these days. -- Gary R. Van Sickle Brewer. Patriot. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/