delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1998/01/23/19:15:29

From: "Andrew Crabtree" <andrewc AT rosemail DOT rose DOT hp DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: use memory more than 1MB
Date: Fri, 23 Jan 1998 15:00:48 -0800
Organization: Hewlett Packard
Lines: 19
Message-ID: <6ab7ec$qmb$1@rosenews.rose.hp.com>
References: <01bd26e6$b95daea0$0100007f AT localhost> <34C81A06 DOT 18AF AT cs DOT com>
NNTP-Posting-Host: ros51675cra.rose.hp.com
Mime-Version: 1.0
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

John M. Aldrich wrote in message <34C81A06 DOT 18AF AT cs DOT com>...
>You should NEVER put large objects on the stack, particularly not the
>way you do it here.
I think depending on background many programmers do just this.  The 'NEVER'
clause is pretty djgpp specific, not 'C' language specific.  Most unixes
will grow
the stack automatically as needed (linux, hpux), and don't have a small
fixed
size one like djgpp.

>You can also increase the default stack size, but that is a really
>horrid way to get the above code to work.
Sure, for this case it is.  But when porting gnu software that uses alloca
heavily
I think increasing stack size is reasonable...

Andy

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019