Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Mon, 15 Aug 2005 09:58:08 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: Re: Cygwin.dll crash, alloca and custom stack
Message-ID: <20050815075808.GR2816@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
References: <602EF4562299D711978800065BEECE9A0D2D30D6 AT cbrml50 DOT ag DOT gov DOT au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <602EF4562299D711978800065BEECE9A0D2D30D6@cbrml50.ag.gov.au>
User-Agent: Mutt/1.4.2i

On Aug 15 16:52, Bitmead, Chris wrote:
> 
> >Yes, I know.  Unless I implement this *crucial* bit of functionality it
> >is possible that the space time continuum will implode.
> 
> I see, so any API that you personally have no use for should be mocked.
> 
> >However, since it is not currently implemented, since there is no sign
> >of an implementation on the horizon, and since it may be impossible to
> >implement for Windows, that does present a problem for your
> >implementation on cygwin.

Translation:

http://cygwin.com/acronyms/#SHTDI
http://cygwin.com/acronyms/#PTC


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/