Re: Images and libraries (was: OBJECTS.FS Question)

Bruce McFarling <agila61@[EMAIL PROTECTED]
> writes:
>On Mar 28, 4:48 pm, an...@[EMAIL PROTECTED]
 (Anton Ertl)
>wrote:
>
>> In any case, there is no reason to make the Memory Allocation wordset
>> a second-class citizen for programs.
>
>Dynamically allocated memory is ... uhm, dynamically allocated?

And?  All memory that a Forth program allocates is allocated at
run-time (that's what's usually meant by "dynamically allocated"),
both ALLOTed memory and ALLOCATEd memory.  Consider:

50 allocate throw constant buf1
here 50 allot constant buf2

Would you say that the memory for buf2, which was allocated later,
is less dynamic than the memory for buf1?

BTW, searching for "dynamic" in the standard do***ent, I see only one
occurence of something like "dynamic allocation", in the definition of
WORDLIST; there is no occurence of "dynamic" in chapter 14 (on the
Memory Allocation wordset).

- 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