Xref:	news2.mv.net comp.os.msdos.djgpp:6840
From:	lehmann AT mathematik DOT th-darmstadt DOT de (Alexander Lehmann)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Flat Memory Questions
Date:	30 Jul 1996 18:38:18 GMT
Organization:	Technische Hochschule Darmstadt
Lines:	24
Message-ID:	<4tlkqq$1nsr@rs18.hrz.th-darmstadt.de>
References:	<720 DOT 9607281807 AT ws-ai5 DOT dur DOT ac DOT uk> <31fd8516 DOT sandmann AT clio DOT rice DOT edu>
NNTP-Posting-Host:	fb0409.mathematik.th-darmstadt.de
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Charles Sandmann <sandmann AT clio DOT rice DOT edu> wrote:
: > Array is put on the stack. But there is only 256Kb on the stack, so the rest
: > of your stack is all over your program. Anyway it is bad practice to use large
: > amounts of stack. You should allocate it dynamically if you want big amounts
: > of memory.

: "Using large amounts of stack" isn't bad practice in general - just on systems
: that aren't properly implemented :-)  (Hey, I'm allowed to bash what I wrote!)

: This is just a big wart on the DPMI 0.9 stuff - DJGPP V1.x under non-DPMI
: didn't have it, VMS doesn't have it, unix doesn't have it, etc.

Well, unix usually has at least maximum stack growth limit, otherwise
it wouldn't be able to distinguish between a wild pointer and a very
large array on the stack. (at least I think that's the reason).


bye, Alexander

-- 
Alexander Lehmann,                                  |  "On the Internet,
alex AT hal DOT rhein-main DOT de  (plain, MIME, NeXT)         |   nobody knows
lehmann AT mathematik DOT th-darmstadt DOT de (plain)          |   you're a dog."
!!CHANGED!! <URL:http://www.mathematik.th-darmstadt.de/~lehmann/>

- Raw text -