Groups > comp.lang.forth > #19128

Re: Understanding Forth's memory allocation

From	Andrew Haley <andrew29@littlepinkcloud.invalid>
Subject	Re: Understanding Forth's memory allocation
Newsgroups	comp.lang.forth
References	<5571ef48-2142-4300-8191-415aff5214e6@googlegroups.com> <dc0f36fd-07a1-4755-8274-7c9603c87f70@googlegroups.com>
Message-ID	<kJSdnRGUSfoc1J_MnZ2dnUVZ_oWdnZ2d@supernews.com> (permalink)
Date	2013-01-25 02:59 -0600

Show all headers | View raw

AKE <assadebrahim2000@gmail.com> wrote:
> Not sure why that got posted suddenly.
> 
> What has me puzzled is why the 'create' word advances the heap
> pointer to the next cell.
> 
> My understanding from the documentation is that the 'here' word
> points to the NEXT unallocated cell of memory.
> 
> In which case, in principle, 'create x' could simply assign x the
> value of here.  But instead it seems to advance the here pointer one
> cell ahead, set x to this cell, and sets the value of the cell it
> just left behind to 49 (decimal).

CREATE may or may not use memory at HERE .  On some Forth systems,
everything is allocated in one space: dictionary entries, variables,
and code.  On other Forth systems there may be several memory spaces.

Andrew.

Thread

Understanding Forth's memory allocation AKE <assadebrahim2000@gmail.com> - 2013-01-24 12:29 -0800
  Re: Understanding Forth's memory allocation AKE <assadebrahim2000@gmail.com> - 2013-01-24 12:35 -0800
    Re: Understanding Forth's memory allocation Jason Damisch <jasondamisch@yahoo.com> - 2013-01-24 13:21 -0800
      Re: Understanding Forth's memory allocation Mark Wills <markrobertwills@yahoo.co.uk> - 2013-01-24 13:53 -0800
        Re: Understanding Forth's memory allocation AKE <assadebrahim2000@gmail.com> - 2013-01-24 14:14 -0800
          Re: Understanding Forth's memory allocation Jason Damisch <jasondamisch@yahoo.com> - 2013-01-24 16:30 -0800
        Re: Understanding Forth's memory allocation albert@spenarnc.xs4all.nl (Albert van der Horst) - 2013-01-25 14:59 +0000
      Re: Understanding Forth's memory allocation AKE <assadebrahim2000@gmail.com> - 2013-01-24 14:09 -0800
    Re: Understanding Forth's memory allocation Hugh Aguilar <hughaguilar96@yahoo.com> - 2013-01-24 19:11 -0800
      Re: Understanding Forth's memory allocation Jason Damisch <jasondamisch@yahoo.com> - 2013-01-24 19:43 -0800
        Re: Understanding Forth's memory allocation albert@spenarnc.xs4all.nl (Albert van der Horst) - 2013-01-25 15:17 +0000
      Re: Understanding Forth's memory allocation AKE <assadebrahim2000@gmail.com> - 2013-01-24 23:14 -0800
        Re: Understanding Forth's memory allocation Mark Wills <forthfreak@gmail.com> - 2013-01-25 00:08 -0800
      Re: Understanding Forth's memory allocation Bernd Paysan <bernd.paysan@gmx.de> - 2013-01-25 15:44 +0100
    Re: Understanding Forth's memory allocation "Elizabeth D. Rather" <erather@forth.com> - 2013-01-25 20:54 +1300
    Re: Understanding Forth's memory allocation Andrew Haley <andrew29@littlepinkcloud.invalid> - 2013-01-25 02:59 -0600
      Re: Understanding Forth's memory allocation Coos Haak <chforth@hccnet.nl> - 2013-01-25 19:48 +0100
  Re: Understanding Forth's memory allocation AKE <assadebrahim2000@gmail.com> - 2013-01-24 13:56 -0800
  Re: Understanding Forth's memory allocation Brad Eckert <hwfwguy@gmail.com> - 2013-01-25 08:41 -0800
    Re: Understanding Forth's memory allocation AKE <assadebrahim2000@gmail.com> - 2013-01-25 08:53 -0800
      Re: Understanding Forth's memory allocation Coos Haak <chforth@hccnet.nl> - 2013-01-25 19:54 +0100

csiph-web