Re: THROW codes and ambiguous conditions

Liste des GroupesRevenir à cl forth 
Sujet : Re: THROW codes and ambiguous conditions
De : no.email (at) *nospam* nospam.invalid (Paul Rubin)
Groupes : comp.lang.forth
Date : 10. Jun 2025, 22:11:30
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <878qlz47zx.fsf@nightsong.com>
References : 1 2 3 4 5
User-Agent : Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)
albert@spenarnc.xs4all.nl writes:
Probably there is, revectoring EMIT and forcing the Forth to work
with single characters. Anton Ertl can show how it is done with
gforth.

Yes, but it seems to be implementation specific.  Reasonable point about
<#...  being in CORE.  It always seemed to me that those words should
have been in an extension.

Date Sujet#  Auteur
31 May 25 * THROW codes and ambiguous conditions40dxf
31 May 25 +* Re: THROW codes and ambiguous conditions7Anton Ertl
31 May 25 i+* Re: THROW codes and ambiguous conditions2dxf
3 Jun 25 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 conditions32Hans Bezemer
2 Jun 25  +- Re: THROW codes and ambiguous conditions1dxf
2 Jun 25  `* Re: THROW codes and ambiguous conditions30albert
3 Jun 25   `* Re: THROW codes and ambiguous conditions29dxf
3 Jun 25    +* Re: THROW codes and ambiguous conditions25Anton Ertl
4 Jun 25    i`* Re: THROW codes and ambiguous conditions24dxf
4 Jun 25    i `* Re: THROW codes and ambiguous conditions23sean
5 Jun 25    i  +- Re: THROW codes and ambiguous conditions1dxf
5 Jun 25    i  `* Re: THROW codes and ambiguous conditions21albert
6 Jun01:47    i   +- Re: THROW codes and ambiguous conditions1dxf
6 Jun07:15    i   `* Re: THROW codes and ambiguous conditions19sean
6 Jun12:00    i    `* Re: THROW codes and ambiguous conditions18albert
6 Jun22:06    i     `* Re: THROW codes and ambiguous conditions17sean
7 Jun04:10    i      `* Re: THROW codes and ambiguous conditions16dxf
7 Jun05:26    i       `* Re: THROW codes and ambiguous conditions15sean
7 Jun05:42    i        +- Re: THROW codes and ambiguous conditions1dxf
7 Jun10:43    i        +* Re: THROW codes and ambiguous conditions12Anton Ertl
7 Jun15:06    i        i`* Re: THROW codes and ambiguous conditions11dxf
7 Jun20:58    i        i `* Re: THROW codes and ambiguous conditions10Paul Rubin
8 Jun02:49    i        i  +* Re: THROW codes and ambiguous conditions4Paul 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
10 Jun22:11    i        i  i`- Re: THROW codes and ambiguous conditions1Paul Rubin
8 Jun03:16    i        i  +- Re: THROW codes and ambiguous conditions1dxf
8 Jun08:56    i        i  `* Re: THROW codes and ambiguous conditions4Anton Ertl
8 Jun15:45    i        i   `* Re: THROW codes and ambiguous conditions3dxf
9 Jun12:36    i        i    `* Re: THROW codes and ambiguous conditions2dxf
9 Jun13:24    i        i     `- Re: THROW codes and ambiguous conditions1LIT
7 Jun15:41    i        `- Re: THROW codes and ambiguous conditions1LIT
3 Jun 25    +- Re: THROW codes and ambiguous conditions1John
4 Jun 25    `* 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