Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Thu, 13 Sep 2001 13:56:14 +0200 From: Corinna Vinschen To: cygwin-developers AT cygwin DOT com Subject: Re: daemon Message-ID: <20010913135614.S1285@cygbert.vinschen.de> Reply-To: cygdev Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <1000375038 DOT 6113 DOT 12 DOT camel AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <1000375038.6113.12.camel@lifelesswks>; from robert.collins@itdomain.com.au on Thu, Sep 13, 2001 at 07:57:12PM +1000 On Thu, Sep 13, 2001 at 07:57:12PM +1000, Robert Collins wrote: > 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)? Perhaps a header file which takes __INSIDE_CYGWIN__ into account? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc.