----------------------------------------------------------------------------------
@MSGID:
<7626edf3-1a44-4fb6-b648-1360da7e2a84n@googlegroups.com> 9783be01
@REPLY:
<d1147752-dccd-421e-bc64-b92bd85d4687n@googlegroups.com> 55845d08
@REPLYADDR S Jack <sdwjack69@gmail.com>
@REPLYTO 2:5075/128 S Jack
@CHRS: CP866 2
@RFC: 1 0
@RFC-References:
<6363a6bb-7a1a-4289-9883-d4e9b5569a3e@googlegroups.com> <7829ca3f-be77-4e85-9b3b-7888175ddb18@googlegroups.com>
<4840ada6-9000-435e-a94c-14316451394d@googlegroups.com> <97d4a69e-41d0-4f01-9bf8-c9fda920d961@googlegroups.com>
<77558bd0-77e9-4fcf-9583-9a40eadb899a@googlegroups.com> 1@dont-email.me>
<fa84ccdc-9c06-4b88-9dbe-1ff7edf8a306@googlegroups.com> <c07bdd98-fd72-467d-b9b1-8beec1f479ad@googlegroups.com>
<f6421c00-4be7-433b-9e14-f9292c2ed4a9@googlegroups.com> <5e6a7510.325826043@news.eternal-september.org>
<326cea0e-c960-46db-ae9d-8e0c9489c907@googlegroups.com> <194715b4-52ef-4121-8a3e-f4c30b45098an@googlegroups.com>
<a7acea48-7781-4ad2-bc5b-feca1469d4fan@googlegroups.com> 1@gioia.aioe.org>
<6f01b499-d106-4278-b352-fb37f7c16ec4n@googlegroups.com> 1@dont-email.me>
<72540e7d-0866-4a1c-9067-84305c171250n@googlegroups.com> 1@dont-email.me>
<c1f5a937-56e5-4677-bee5-5724a30676d7n@googlegroups.com> 1@dont-email.me>
<4a00e294-d5a1-43e1-a359-1f4d6ae092d1n@googlegroups.com> <d1147752-dccd-421e-bc64-b92bd85d4687n@googlegroups.com>
@RFC-Message-ID:
<7626edf3-1a44-4fb6-b648-1360da7e2a84n@googlegroups.com>
@TZUTC: -0700
@PID: G2/1.0
@TID: FIDOGATE-5.12-ge4e8b94
On Thursday, September 28, 2023 at 12:34:29 PM UTC-5, John Hart wrote:
> On Thursday, September 28, 2023 at 8:22:52 AM UTC-7, Zbig wrote:
> > > But Fig is directly responsible for where Forth is today. Washing
> > > its hands of fig-Forth (it had served its purpose we were told),
> > > Fig found itself a new role - to facilitate and develop a Forth
> > > Standard through the FST (Forth Standards Team). FST gave us
> > > Forth-79 and Forth-83. Forth-83 was in turn the basis document
> > > of ANS-Forth.
>
> > The good thing about Forth standards is that there are so many
> > to choose from. :D
> In the 90s I proposed Absolute Forth, a simple defining language
to describe Forth variants.
> The idea was to make is so automated tools could convert library
functions from one variant to
> another. At the time the idea went over like a lead balloon, probably because
Toyed with some ideas along that line:
i. Standard pigeon Forth
Only specifies the gist of the word. Since its not an executable
it can be a simple affair without "optimizations" just focusing
on intended behavior.
i. Standard behavior san names.
Specified behaviors with given numeric labels. User use any
names they want to fit a dialog that express their program.
And multiple names can be used with the same behavior to
fit the context where applied.
(Went so far as to build Forth with pointer in the name field
so names could be kept in one block and switched out with
with alternate name sets.)
Converting one Forth from and to standard forth is just a sed file.
It`s not completely straight forward as sometimes order matters.
--
me
--- G2/1.0
* Origin: usenet.network (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5058/104 5075/128
@PATH: 5075/128 5020/1042 4441