Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.forth > #19132

Re: Understanding Forth's memory allocation

Show all headers | View raw

Hugh Aguilar wrote:

> On Jan 24, 1:35 pm, AKE <assadebrahim2...@gmail.com> wrote:
>> My understanding from the documentation is that the 'here' word
>> points to the NEXT unallocated cell of memory.
> 
> This is another thing that ANS-Forth screwed up. The code and data
> "may" be intermingled, or they "may" be separate. So, as a practical
> matter, you have to assume that they are intermingled.

Yes.

> This is the
> problem with ANS-Forth --- overuse of the word "may" --- it is a
> standard that doesn't standardize, but pretty much anything "may" be
> considered standard.

A standard codifies common practise, and leave undefined where no common 
practise has arrived yet.  I think you are simply mistaken what the 
purpose of a standard is.  You propose "StrongForth" as "alternative 
standard", but it isn't a standard, it will be just another incompatible 
system:

http://xkcd.com/927/

The way to reduce the "maybe" is not to smoke Marlboro, but to convince 
people that a particular decision is worth to implement, and thereby 
common practise emerges.  E.g. in Forth200x we have eliminated the 
"maybe" unified floating point stack, as the common (and only sane) way 
to do it is with a separate stack.

A standard is a compromise between different people.  If you don't want 
to compromise, fine, but you have to go Chuck's way (or the way of my 
footer): You have to do it yourself.  This is a fine tradition in the 
Forth world.  But it's not a standard.

-- 
Bernd Paysan
"If you want it done right, you have to do it yourself"
http://bernd-paysan.de/

Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

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