Deutsch   English   Français   Italiano  
<66a26d3b$1@news.ausics.net>

View for Bookmarking (what is this?)
Look up another Usenet article

Date: Fri, 26 Jul 2024 01:20:28 +1000
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
From: dxf <dxforth@gmail.com>
Subject: Re: History of CREATE...DOES> ?
Newsgroups: comp.lang.forth
References: <2024Jul25.141725@mips.complang.tuwien.ac.at>
Content-Language: en-GB
In-Reply-To: <2024Jul25.141725@mips.complang.tuwien.ac.at>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: news.ausics.net
Message-ID: <66a26d3b$1@news.ausics.net>
Organization: Ausics - https://newsgroups.ausics.net
Lines: 23
X-Complaints: abuse@ausics.net
Path: ...!weretis.net!feeder9.news.weretis.net!news.bbs.nz!news.ausics.net!not-for-mail
Bytes: 2025

On 25/07/2024 10:17 pm, Anton Ertl wrote:
> fig-Forth has <BUILDS...DOES> (and the associated implementation with
> an extra cell that points to the threaded code behind DOES>).
> Forth-79 standarizes CREATE...DOES>; and a popular implementation of
> that is to trampoline through the place behind DOES> to the actual
> code address.  Where did that implementation and CREATE..DOES> in
> general come from?
> 
> My guess is that it did not come from Forth, Inc.: At the time of
> Forth-79 AFAIK Forth, Inc.'s Forths were miniForth and microForth.
> And given that fig-Forth started out as a port of microForth to the
> 6502, I doubt that Forth, Inc. used CREATE..DOES>.  Also, Forth,
> Inc. ignored Forth-79 (IIRC Elizabeth Rather described it as
> inconsistent or some other statement that she would not have made if
> Forth, Inc. had actually accepted and implemented Forth-79).
> 
> At least dxf is very well versed in historic Forth developments.
> Maybe he or somebody else can answer my question: Where did the
> implementation described above and CREATE..DOES> in general come from?

There's a detailed description of the origins of these in Chuck's
address "FORTH: The Last Ten Years ..." (FD V1N6. p72).  They all
came from Forth Inc but mostly not Chuck.  He needed help!