I fear that this sentence from the dictionary entry for hasMemory is correct:
This function is only partially implemented, and may not return
useful values on some platforms. It is included in Revolution for
compatibility with imported SuperCard projects.
See also
http://quality.runrev.com/qacenter/show_bug.cgi?id=6791
Poor memory handling is, for me, one of the biggest reasons not to use Rev for
certain projects. If it doesn't bite you, you're fine, and one of the great
benefits of Rev is not having to worry about memory; but if it does bite you,
you're SOL. Also see also
http://quality.runrev.com/qacenter/show_bug.cgi?id=2772
Ben
On 08/07/2010 18:55, william humphrey wrote:
Phil
I've been using a fairly complex system of stacks for years now in
RunRev and never heard of or felt a need for freeing up memory. It
seems to me it allocates a certain amount on start-up and stays that
way through out. Of course all my data is stored separately in an
external database (valentina).
Bill
On Thu, Jul 8, 2010 at 1:32 PM, Phil Davis<[email protected]> wrote:
Hi folks,
Almost a year ago I posted the following with no response, and now the need
to know has come up again:
In ancient times I used the hasMemory() function to force garbage
collection and free up memory. But maybe it only worked that way in
SuperCard... can anyone comment on its effectiveness in Revolution?
Any takers?
--
Phil Davis
PDS Labs
Professional Software Development
http://pdslabs.net
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
