Re: OBJECTS.FS Question

Doug Hoffman <no.spam> writes:
>If I then make a snapshot image of my Forth system and re-launch that I 
>am unable to get my object x to do anything.

Most Forth systems don't save ALLOCATEd memory when you make an image,
so when you use an image, any ALLOCATEd data is gone.  objects.fs uses
ALLOCATE and RESIZE to store some of the data on cl*****, and that
would then be lost.  I guess that's the problem you see.

>  Worse, I cannot even reload the above code 
>starting with 'interface selector val ...'.

There is already something stored in ALLOCATEd memory when you include
objects.fs (in particular, parts of the definition of the OBJECT
class).

Should we change the Forth systems to also save ALLOCATEd memory,
should we change applications and libraries to avoid ALLOCATEd memory,
or should we just be happy with loading applications from the start on
every startup (and make the systems compile fast enough)?

- anton
-- 
M. Anton Ertl  http://www.complang.tuwien.ac.at/anton/home.html
comp.lang.forth FAQs: http://www.complang.tuwien.ac.at/forth/faq/toc.html
     New standard: http://www.forth200x.org/forth200x.html
   EuroForth 2008:
http://www.complang.tuwien.ac.at/anton/euroforth/ef08.html