delorie.com/archives/browse.cgi | search |
From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: allocating big chunks with djgpp |
Date: | Sun, 09 Feb 2003 10:13:54 CST |
Organization: | Rice University, Houston TX |
Lines: | 11 |
Message-ID: | <3e467e42.sandmann@clio.rice.edu> |
References: | <b25thp$g512 AT imsp212 DOT netvigator DOT com> |
NNTP-Posting-Host: | clio.rice.edu |
X-Trace: | joe.rice.edu 1044807377 29607 128.42.105.3 (9 Feb 2003 16:16:16 GMT) |
X-Complaints-To: | abuse AT rice DOT edu |
NNTP-Posting-Date: | 9 Feb 2003 16:16:16 GMT |
X-NewsEditor: | ED-1.5.9 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
> with 16-bit DOS compilers, char buffer[30000][81] seems unrealistic and > infeasible. Now with Djgpp, how do I allocate such a big buffer in terms of > what syntax is used? or leave that code snippet intact and the linker will > function okay? The code snippet should work intact if it is a static variable and not an automatic variable. If it is an automatic varaible (inside a function for example) it would be put on the stack - and that's too big for DJGPP's default stack. You can change the stack size to work around this, but other ways are to make it a global/static variable or to use malloc() to allocate it.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |