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
Subject:	RE: How to make DLLs in cygwin for MSVC and BCB
From:	Max Kaehn <slothman AT electric-cloud DOT com>
To:	cygwin AT cygwin DOT com
In-Reply-To:	<SERRANOt0Y57FCulKtR000001a1@SERRANO.CAM.ARTIMI.COM>
References:	<SERRANOt0Y57FCulKtR000001a1 AT SERRANO DOT CAM DOT ARTIMI DOT COM>
Date:	Thu, 23 Jun 2005 12:09:18 -0700
Message-Id:	<1119553758.6224.32.camel@fulgurite>
Mime-Version:	1.0
X-IsSubscribed:	yes

On Thu, 2005-06-23 at 18:18 +0100, Dave Korn wrote:
>   Sorry, but why isn't that 4k at the *TOP* of the stack?  It sure looks
> that way to me, unless cygwin stacks grow upward!

You're mixing the metaphors. :-)  The top of a stack is where you push
something down onto the stack.  The bottom of the stack is at the 
other end.  There happens to be an implementation detail of stacks
growing downward in memory, so the bottom of the stack is at the top 
of the memory allocated to the stack.  I always found that puzzling,
too...




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

- Raw text -