In article <mac-perl.v03110703b190b1a734c3@[206.168.221.110]>, Eric Dobbs <dobbs@visionlink.org> wrote: >... >>When >>FoxBase+ needed more memory in order to run something, it went out and >>used the system's heap stack in order to do so. >... >>Could MacPerl be made to work this way? > >Please, not until MacOS has protected memory! Using memory from another heap (temporary memory is preferred today over allocating memory from the system heap) is really no more safe or unsafe than "regular" memory in terms of memory protection. If an app has bugs which allows it to write to unintended areas of memory it will cause problems whether or not it uses temp memory; if it doesn't, it won't. So this could be done with MacPerl, but I doubt that it's a priority for Matthias. Threading (allowing multiple scripts to run simultaneously) seems like a bigger priority. -- __________________________________________________________________________ Jeff Clites Online Editor http://www.MacTech.com/ online@MacTech.com MacTech Magazine __________________________________________________________________________ ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch