Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <42BB4369.3010105@hones.org.uk>
Date: Fri, 24 Jun 2005 00:19:05 +0100
From: Cliff Hones <cliff AT hones DOT org DOT uk>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: How to make DLLs in cygwin for MSVC and BCB
References: <SERRANOt0Y57FCulKtR000001a1 AT SERRANO DOT CAM DOT ARTIMI DOT COM> <1119553758 DOT 6224 DOT 32 DOT camel AT fulgurite>
In-Reply-To: <1119553758.6224.32.camel@fulgurite>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Max Kaehn wrote:
> 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...

Reminds me of the probably apocryphal WWII story about a new type of
tank shell.  Normal shells are always crated with the sharp-end up, but
the new ones were unsafe stored that way.  The boxes were marked
"To avoid confusion, the bottom of these crates has been marked TOP."

-- Cliff

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