Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Subject: daemon
From: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
To: cygwin-developers AT cygwin DOT com
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Evolution/0.13 (Preview Release)
Date: 13 Sep 2001 19:57:12 +1000
Message-Id: <1000375038.6113.12.camel@lifelesswks>
Mime-Version: 1.0
X-OriginalArrivalTime: 13 Sep 2001 09:44:07.0778 (UTC) FILETIME=[A20E8420:01C13C38]

The daemon is coming long nicely. I've a nearly complete transport layer
class, with a factory and virtual methods, to encapsulate all the
security impersonation and handshaking needed, allowing us to focus on
the daemon for now, or the transport or both.

However, I have a little question.

I want to use the same class inside and outside cygwin, for consistency,
and to prevent skew problems. The issue is that things like accept()
outside of cygwin are fine, but in cygwin you need to use
cygwin_accept().

So... is there someway to resolve that, without compiling the source
file twice (which is one way) or having a symlink to the source under a
different name (ugly IMO)?

Rob