Kirk> It's dangerous to admit to being a Windows/Cygwin expert, and I
Kirk> don't know that I qualify, but here is a possibility: IIRC,
Kirk> C-Reduce forks a bunch to do its work. fork() isn't directly
Kirk> supported by Windows, so Cygwin has to fake it and it is an
Kirk> expensive operation. My guess is that this is where the
Kirk> performance hit is coming from.
FWIW, this lends support to Konstantin Tokarev's idea that C-Reduce should
support Perl-based predicates in addition to shell-based (fork-fork-fork) ones.
If C-Reduce on Windows is going to be slow because of Cygwin's fork, and we
care about this, we should perhaps avoid either fork or Cygwin altogether.
Eric.
--
-------------------------------------------------------------------------------
Eric Eide <[email protected]> . University of Utah School of Computing
http://www.cs.utah.edu/~eeide/ . +1 (801) 585-5512 voice, +1 (801) 581-5843 FAX
