X-Spam-Check-By: sourceware.org Date: Fri, 17 Feb 2006 15:49:04 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: _kbhit Message-ID: <20060217204904.GA24222@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <20060216011405 DOT 9CC6E2681 AT dot DOT warande DOT net> <001e01c632af$25414d20$020aa8c0 AT DFW5RB41> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Fri, Feb 17, 2006 at 12:27:52PM -0800, Shankar Unni wrote: >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 >:-). > >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. Details, details. The bottom line comes down to sheer will. If someone really wants _kbhit then, with enough reinstalls, and email messages stating that fact, it will surely happen regardless of runtimes or exclusionary principles. Human spirit and indomitable determination trumps all! cgf -- 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/