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 Subject: RE: OT: possible project/research project Date: Thu, 21 Mar 2002 20:20:50 +1100 MIME-Version: 1.0 Message-ID: Content-Type: text/plain; charset="us-ascii" X-MS-Has-Attach: X-MS-TNEF-Correlator: X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message From: "Robert Collins" To: "Gary R. Van Sickle" , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g2L9MvK16060 > -----Original Message----- > From: Gary R. Van Sickle [mailto:g DOT r DOT vansickle AT worldnet DOT att DOT net] > Sent: Thursday, March 21, 2002 2:25 PM > #1 is basically the same as what you propose, though I'm not > sure I'm wild about the DLL idea; if everything's a builtin, > why not just statically link? Several reasons. 1) I'm a user and I want foo-version of bar. How do I get that? 2) I'm in cmd.exe and want to run bar - does it still exist? 3) I'm running setup.exe and ls has been updated - do I download an updated fileutils package or an updated bash package? 4) I'm a user and I want to add a new builtin. One thing I'm considering doing is contributing a posix_spawn and posix_spawnp to cygwin, to enhance the vfork capability. That should allow patchs to be contributed upstream to gcc etc to remove fork - because posix_spawn is a standard, it wouldn't be see as a cygwin hack. Rob -- 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/