public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: Yitzchak Scott-Thoennes <sthoenna@efn.org>
To: cygwin-talk@cygwin.com
Subject: Re: cygwin fork problem maybe?
Date: Wed, 07 Jun 2006 06:19:00 -0000	[thread overview]
Message-ID: <20060607061909.GA2592@efn.org> (raw)
In-Reply-To: <4485EB68.9F685880@dessent.net>

On Tue, Jun 06, 2006 at 01:54:00PM -0700, Brian Dessent wrote:
> Linda W wrote:
> 
> > Windows just doesn't support forking at all, as far as I know.
> > activeperl emulates forking using win32 threads. I don'tknow how cygwin
> > handles it, but my guess is that it's not very well :-(
> 
> This smells like total FUD.  This person that admittedly does not use
> Cygwin nor obviously know anything about Cygwin says that it's a fork
> problem and that's that?  Fork may be a problem for Activestate but
> Cygwin fully emulates fork just fine, as does Cygwin's perl.  The Cygwin
> DLL goes to extreme lengths to make sure this work.

Debatably, not as extreme as the lengths AS Perl goes to :)

           reply	other threads:[~2006-06-07  6:19 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <4485EB68.9F685880@dessent.net>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060607061909.GA2592@efn.org \
    --to=sthoenna@efn.org \
    --cc=cygwin-talk@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).