On Wed, 15 Jan 2003 17:16:25 +0100, Bart Lateur wrote:
>You might try to wrap it all in an eval { ... } , but I have some doubts
>if it'll work well. "Out of memory" would seem to be one of those very low
>level errors, that leaves MacPerl behind in a state of shock. I doubt if
>you can do much of use with it, after that.
I'm afraid you're right. After 2 or 3 "Out of memory" conditions, MacPerl behaves
funny, or crashes the Mac.
On Thu, 16 Jan 2003 19:01:39 -0800, Bruce Van Allen wrote:
>If large files are anticipated, I try to determine their size before
>slurping, and not slurp if a file seems too large.
I had such ideas, and you gave me good examples. I was wondering if there is a method,
or a hack, to find out the amount of available memory at some point in executing a
Perl script. It must be hiding somewhere in the MacOS, because freewares such as
Memory Mapper display it.
Thanks
====
