Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!weretis.net!feeder4.news.weretis.net!rt.uk.eu.org!aioe.org!.POSTED!not-for-mail
From: "Rod Pemberton" <dont_use_email@xnohavenotit.cnm>
Newsgroups: comp.lang.forth
Subject: quick review of <BUILDS and CREATE history
Date: Sun, 19 Jan 2014 13:15:44 -0500
Organization: Aioe.org NNTP Server
Lines: 31
Message-ID: <op.w9x40in85zc71u@localhost>
NNTP-Posting-Host: CNsg4fVcCsvs3UaOgZtQCw.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
X-Complaints-To: abuse@aioe.org
User-Agent: Opera Mail/12.16 (Linux)
X-Notice: Filtered by postfilter v. 0.8.2
Xref: csiph.com comp.lang.forth:27952


Okay, let's see if I get this correct ...

<BUILDS originally worked with DOES> .
<BUILDS was defined as 0 CONSTANT in fig-Forth.
CONSTANT used an early limited version of
CREATE to build a dictionary header.
Then, <BUILDS was obsoleted, and CREATE
was enhanced to work in place of both the
limited CREATE and <BUILDS.  That gave rise
to CREATE ... DOES> .  Next, :NONAME was
created to essentially do what the early
limited CREATE did but without writing a name
into the dictionary header.  Many systems also
have a non-standard word HEADER to do this too.
Now, you guys are wanting to restore the original
<BUILDS because the more powerful CREATE doesn't
work as well in embedded systems that use flash
memory, have limited writes, and separate address
spaces.

Is this correct?

Why does it feel like I'm going around in circles?

Is this a prime example of poor factoring?

Can <BUILDS now be constructed with :NONAME ?


Rod Pemberton