On Fri, 21 Aug 1998, Mark Manning/Muniz Eng. wrote: > Bart Lateur wrote: > > Hmm... This makes one daydream. What if MacPerl could get more memory > > from the system pool, if what was allocated to the program just isn't > > enough. Just like the Finder does. > > Been there - done that. :-) Requested this feature some time back and > others were not too happy about it. However, BBEdit does this, FoxBase > does it, FoxPro does it, MS-Word does it. Bees do it, birds do it, even > MacPerl should do it - let's do it - let's use VM. :-) Sweet! I love the jazz reference! I agree, using temp memory seems pretty logical to me. At first glance. Perhaps others know why it might not be so. But no matter what, MacPerl has no excuse for crashing when it runs of memory or stack space or whatever. Good Programs don't do that, they choke gracefully and die without bringing down the whole system. Sure, this is much harder on MacOS than Unix; that's entirely beside the point. It should be implicitly part of the MacPerl goal (and I imagine it is). I'd be happy to donate my StdLogs and offending REs. -- MattLangford ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch