The little I know is that in Supercard, it would return to you whether or not a given number of bytes could be allocated. IIRC (and I might not!) people tended to use it in order to detect a low-memory situation, i.e. if hasMemory(1024*1024) failed then there was less than 1MB of memory to be had and that might be trouble.

Since Supercard is Mac-only, and the function was first written for OS 9 where each application has a fixed memory allocation, it was probably well-defined if still a bit unusual. I'm guessing the Rev "half implementation" gets stuck on the meaning of the whole thing on other OS'es with swap files and shared memory and all of that good stuff.

Conclusion- I would stay way unless you want something specific on MacOS and can verify that it works.

FWIW...

All-

Does anyone have any clues about the "hasMemory" function? In the
documentation I see:

Comments:
This function is only partially implemented, and may not return useful
values on some platforms. It is included in Transcript for
compatibility with imported SuperCard projects.

That alone would keep me from using it, but I'm curious about what
"partially implemented" means.

--
-Mark Wieder
 [EMAIL PROTECTED]

_______________________________________________
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution



_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to