Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-ID: <602EF4562299D711978800065BEECE9A0D2D30D2@cbrml50.ag.gov.au> From: "Bitmead, Chris" To: "'cygwin AT cygwin DOT com'" Subject: RE: Cygwin.dll crash, alloca and custom stack Date: Mon, 15 Aug 2005 11:04:26 +1000 MIME-Version: 1.0 Content-Type: text/plain >All major languages in use today have a runtime - C is no different. On UNIX/Linux, its mostly (if not always) >called libc (glibc being the GNU variant used on most Linux systems). Well I don't think of libc as part of the C language proper because I spent a number of years programming in a version of C that didn't have any of the normal functions one normally associates with libc, like printf and all those other functions you'll find in the ansi standard. libc doesn't implement any of the features of the C language proper, unlike other languages that have a "runtime" that implements actual language features like garbage collectors, object systems and so on. libc is an optional library that you can choose to use or not use in your C program. If you want to include the standard library as part of "C", then I suppose you could say it is a runtime, but that kindof makes "runtime" a meaningless term, when it includes pedestrian stuff like atoi. ----------------------------------------------------------------- If you have received this transmission in error please notify us immediately by return e-mail and delete all copies. If this e-mail or any attachments have been sent to you in error, that error does not constitute waiver of any confidentiality, privilege or copyright in respect of information in the e-mail or attachments. -- 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/