This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
RE: OT: possible project/research project
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- To: "Gary R. Van Sickle" <g dot r dot vansickle at worldnet dot att dot net>,<cygwin at cygwin dot com>
- Date: 2002年3月21日 20:20:50 +1100
- Subject: RE: OT: possible project/research project
> -----Original Message-----
> From: Gary R. Van Sickle [mailto:g.r.vansickle@worldnet.att.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/