Re: THROW codes and ambiguous conditions

Liste des GroupesRevenir à cl forth 
Sujet : Re: THROW codes and ambiguous conditions
De : albert (at) *nospam* spenarnc.xs4all.nl
Groupes : comp.lang.forth
Date : 06. Jun 2025, 12:00:04
Autres entêtes
Organisation : KPN B.V.
Message-ID : <nnd$470dff8c$593b4849@31279367604044df>
References : 1 2 3 4
User-Agent : trn 4.0-test77 (Sep 1, 2010)
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.

Date Sujet#  Auteur
31 May 25 * THROW codes and ambiguous conditions37dxf
31 May 25 +* Re: THROW codes and ambiguous conditions7Anton Ertl
31 May 25 i+* Re: THROW codes and ambiguous conditions2dxf
3 Jun21:48 ii`- Re: THROW codes and ambiguous conditions1sjack
31 May 25 i`* Re: THROW codes and ambiguous conditions4Anton Ertl
1 Jun 25 i `* Re: THROW codes and ambiguous conditions3albert
1 Jun 25 i  `* Re: THROW codes and ambiguous conditions2Anton Ertl
1 Jun 25 i   `- Re: THROW codes and ambiguous conditions1albert
1 Jun 25 `* Re: THROW codes and ambiguous conditions29Hans Bezemer
2 Jun05:58  +- Re: THROW codes and ambiguous conditions1dxf
2 Jun11:44  `* Re: THROW codes and ambiguous conditions27albert
3 Jun04:23   `* Re: THROW codes and ambiguous conditions26dxf
3 Jun07:10    +* Re: THROW codes and ambiguous conditions22Anton Ertl
4 Jun15:44    i`* Re: THROW codes and ambiguous conditions21dxf
4 Jun20:25    i `* Re: THROW codes and ambiguous conditions20sean
5 Jun07:09    i  +- Re: THROW codes and ambiguous conditions1dxf
5 Jun11:17    i  `* Re: THROW codes and ambiguous conditions18albert
6 Jun01:47    i   +- Re: THROW codes and ambiguous conditions1dxf
6 Jun07:15    i   `* Re: THROW codes and ambiguous conditions16sean
6 Jun12:00    i    `* Re: THROW codes and ambiguous conditions15albert
6 Jun22:06    i     `* Re: THROW codes and ambiguous conditions14sean
7 Jun04:10    i      `* Re: THROW codes and ambiguous conditions13dxf
7 Jun05:26    i       `* Re: THROW codes and ambiguous conditions12sean
7 Jun05:42    i        +- Re: THROW codes and ambiguous conditions1dxf
7 Jun10:43    i        +* Re: THROW codes and ambiguous conditions9Anton Ertl
7 Jun15:06    i        i`* Re: THROW codes and ambiguous conditions8dxf
7 Jun20:58    i        i `* Re: THROW codes and ambiguous conditions7Paul Rubin
8 Jun02:49    i        i  +* Re: THROW codes and ambiguous conditions3Paul Rubin
8 Jun04:36    i        i  i+- Re: THROW codes and ambiguous conditions1dxf
8 Jun09:07    i        i  i`- Re: THROW codes and ambiguous conditions1Anton Ertl
8 Jun03:16    i        i  +- Re: THROW codes and ambiguous conditions1dxf
8 Jun08:56    i        i  `* Re: THROW codes and ambiguous conditions2Anton Ertl
8 Jun15:45    i        i   `- Re: THROW codes and ambiguous conditions1dxf
7 Jun15:41    i        `- Re: THROW codes and ambiguous conditions1LIT
3 Jun09:43    +- Re: THROW codes and ambiguous conditions1John
4 Jun03:03    `* Re: THROW codes and ambiguous conditions2dxf
6 Jun11:47     `- Re: THROW codes and ambiguous conditions1Hans Bezemer

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal