Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uunet!mcsun!unido!ira.uka.de!smurf!urlichs
From: urlichs@smurf.sub.org (Matthias Urlichs)
Newsgroups: comp.sys.mac.programmer
Subject: Re: How to malloc memory VERY dynamically and not out of app heap?
Message-ID: <5CL_43A@smurf.sub.org>
Date: 30 Mar 91 23:57:14 GMT
References: <669949449.1@mmug.fidonet.org.org> <2029@seti.inria.fr> <1991Mar27.203458.24039@ux1.cso.uiuc.edu>
Organization: University of Karlsruhe, FRG
Lines: 20

Yet another virtual-memory vs. the-application-manages-its-data war...

I suggest: When in doubt, get both.

A text editor is a very good example how an application benefits greatly by
doing its personal memory management. The editor isn't going to be any more
complex just because not all of the text is in memory at any one time, and
the user can't look at the whole text at the same time anyway. ;-).

A color picture editor, however, will be a _lot_ easier to program&debug if
it can just allocate the picture as a big chunk o' memory, use the standard
32-bit QD calls, and let the system handle swapping the actual data
if necessary.

Sweeping generalizations as to which method is the all-out better one
aren't going to help. (IMHO.)

-- 
Matthias Urlichs -- urlichs@smurf.sub.org -- urlichs@smurf.ira.uka.de     /(o\
Humboldtstrasse 7 - 7500 Karlsruhe 1 - FRG -- +49-721-621127(0700-2330)   \o)/