Newsgroups: comp.lang.forth
Subject: Re: THROW codes and ambiguous conditions
References: <f827ba6fc80427f3ce0317835bd8ae47a4445e07@i2pn2.org> <101q6ik$10htc$1@dont-email.me> <nnd$7d6e16de$78c9f5b5@7d0d4c583323cd1e> <101u12p$23a54$1@dont-email.me>
From: albert@spenarnc.xs4all.nl
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
Originator: albert@cherry.(none) (albert)
Message-ID: <nnd$470dff8c$593b4849@31279367604044df>
Organization: KPN B.V.
Date: Fri, 06 Jun 2025 13:00:04 +0200
Path: ...!feeds.phibee-telecom.net!3.eu.feeder.erje.net!feeder.erje.net!feeder1.feed.ams11.usenet.farm!feed.usenet.farm!feed.abavia.com!abe004.abavia.com!abp003.abavia.com!news.kpn.nl!not-for-mail
Lines: 66
Injection-Date: Fri, 06 Jun 2025 13:00:04 +0200
Injection-Info: news.kpn.nl; mail-complaints-to="abuse@kpn.com"
Bytes: 3840

In article <101u12p$23a54$1@dont-email.me>,  <sean@conman.org> wrote:
>It was thus said that the Great albert@spenarnc.xs4all.nl once stated:
>> Good work, 12K is justly considered tiny.
>
>  Thank you.
>
>>>[1]    I implemented CORE, CORE-EXT, DOUBLE, DOUBLE-EXT, EXCEPTION,
>>>       EXCEPTION-EXT, LOCAL, LOCAL-EXT, TOOLS, some of TOOLS-EXT [3],
>>>       SEARCH, SEARCH-EXT, STRING and STRING-EXT.
>>>
>>>[2]    https://github.com/spc476/ANS-Forth
>>>
>>>[3]    Words implemented from TOOLS-EXT: AHEAD, BYE, CS-PICK, CS_ROLL, N>R,
>>>       NAME>COMPILE, NAME>INTERPRET, NAME>STRING, NR>, STATE,
>>>       TRAVERSE-WORDLIST, [DEFINED], [ELSE], [IF], [THEN], [UNDEFINED].
>>>
>>>[4]    When reading about it [5], I decided I didn't want anything to do
>>>       with that quagmire of a word.
>>>
>>>[5]    https://forth-standard.org/standard/tools/SYNONYM
>>
>> You have included a lot of words that I considered not needed for
>> a tiny Forth.
>
>  Such as?  One goal (which kind of went to the wayside as I was writing)
>was to use as much of standard Forth as possible to write the code (and less
>to implement in assembly), thus the inclusion of AHEAD, CS-ROLL, etc.  But
>once I past 8K with pretty much CORE, CORE-EXT, SEARCH, SEARCH-EXT and the
>ones I was using from TOOLS-EXT, I had past 8K, so I decided I might as well
>include DOUBLE, DOUBLE-EXT, STRING, STRING-EXT, LOCAL and LOCAL-EXT.  At
>that point, I might as well make a Forth that was useful for as many people
>as possible, while not locking it into a particular system.  That's why I
>didn't bother with BLOCK, BLOCK-EXT, FACILITY or FACILITY-EXT (leaving that
>for the others to write for their system).

Adding more wordsets is not making it useful for as many people as possible.
Leaving out the FACILTY wordset ( SEE DUMP WORDS LOCATE) make a system
virtually unusable.
Using BLOCKS to store all words that belong in a library, that I found extremely
useful. ( WANT ).
Adding D2/ D2* D2> 2VARIABLE is in bad taste. They clutter up the output of
WORDS. Try WORDS in gforth. Can you even check D2* is in there?
Of course traditional formatting words require certain DOUBLE words.

"as many people as possible" . My thought on this, to make it eminently
usable by myself. What I did was writing hundreds of solution programs
to Euler programs, instead of assuming that "more of the standard is better"

>
>> The first time I will ever need CS-PICK I will add it to the library.
>> It is not eligible for a kernel word.
>
>  I wasn't sure if it was needed or not.  It just falls pack to PICK anyway.

You can be sure if you needs it, if you use your forth to program, not?

>
>  -spc

Groetjes Albert
-- 
Temu exploits Christians: (Disclaimer, only 10 apostles)
Last Supper Acrylic Suncatcher - 15Cm Round Stained Glass- Style Wall
Art For Home, Office And Garden Decor - Perfect For Windows, Bars,
And Gifts For Friends Family And Colleagues.