Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site pur-ee.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxj!ihnp4!inuxc!pur-ee!ecn-ee!malcolm From: malcolm@ecn-ee.UUCP Newsgroups: net.lang.c Subject: Re: C stack frame sizes Message-ID: <2400@pur-ee.UUCP> Date: Sun, 2-Dec-84 00:27:07 EST Article-I.D.: pur-ee.2400 Posted: Sun Dec 2 00:27:07 1984 Date-Received: Sun, 2-Dec-84 03:26:04 EST Sender: notes@pur-ee.UUCP Organization: Electrical Engineering Department , Purdue University Lines: 16 Nf-ID: #R:arizona:-1809200:ecn-ee:13100014:000:597 Nf-From: ecn-ee!malcolm Nov 30 21:27:00 1984 I commonly put up to a megabyte into a single stack frame. I write heavy duty number crunching for a living and can't live without C's modularity (compared to Fortrash.) I find it is much more elegant to put all of my temporary arrays on the stack so that they are hidden from other routines and they don't take up memory space except when the routine is active. This is especially a win for rarely called routines. Of course I could use malloc but this would be a real pain in the a**. I wonder what this type of programming style would do to a Berkeley style RISC machine? Malcolm