hasMemory

[Mark Wieder]

Richard Gaskin <ambassador at ...> writes:

> The challenge, however, is that currently most xTalks, including 
> LiveCode, sometimes have difficulty reporting errors in low-memory 
> conditions.  When bad enough, it can sometimes cause a crash before 
> we're able to check "the result" and apply any remedy.

Yes, that is of course what I'm aiming for. There have been problems
in the past with LC (or at least RunRev) misbehaving under low physical
memory conditions, and that's difficult to catch an replicate. Of course,
this all depends on the engine still functioning well enough to handle the
memory reporting functions, so it may just be moot after all.

-- 
 Mark Wieder
 ahsoftware at gmail.com