X-Spam-Check-By: sourceware.org
From: "Gary R. Van Sickle" <g DOT r DOT vansickle AT worldnet DOT att DOT net>
To: <cygwin AT cygwin DOT com>
Subject: RE: _kbhit
Date: Sat, 18 Feb 2006 15:16:06 -0600
Message-ID: <002b01c634d0$892b0e20$020aa8c0@DFW5RB41>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In-Reply-To: <dt5bk9$dv4$1@sea.gmane.org>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

> From: Shankar Unni
> Sent: Friday, February 17, 2006 2:28 PM
> To: cygwin AT cygwin DOT com
> Subject: Re: _kbhit
> 
> Gary R. Van Sickle wrote:
> 
>  > Arend-Jan Westhoff writes:
> >> I cannot confirm your assertion that msvcrt.dll and cygwin1.dll 
> >> cannot be used together.
> 
> > The Gary Exclusion Principle:  Two C runtimes cannot occupy 
> the same 
> > point in space at the same moment in time.
> 
> The problem here is that unfortunately they *can* occupy the 
> same point in space at the same time, with the same bad 
> effects as in science fiction movies when one object 
> materializes in the middle of another :-).
> 

Exactly: Attempting to violate the Gary Exclusion Principle can only result
in tragedy.  In this case, the computer turns into a particle so dense not
even light can escape.

> The problem is that, for instance, some of your malloc calls 
> will link to the cygwin libc, while others (from within the 
> Windows DLLs) will link to MSVCRT, and if you free the 
> pointer with the "other" library, terrible things will happen.

Ah yes, the Gump Uncertainty Principle: You never know which malloc you're
going to get.

-- 
Gary R. Van Sickle
 


--
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/