Re: Why dial-a-standard is not a thing in Forth

On 1 May 2025 at 13:17:27 CEST, "John Doe" <john.doe@myemail.invalid> wrote:

On 1 May 2025 at 03:23:53 CEST, "dxf" <dxforth@gmail.com> wrote:
 

AFAIK on most forth systems exceptions generate either an error code or an
error message (the latter via ABORT" or caught code).  In short, what good
is having both a msg and a code?

 
THROWs are defined to be defined by their throw number. Whether or not a
message is associated with the throw number is a factor of the Forth
implementation.
In VFX, the return to the text interpreter looks for a message associated with
the throw number and displays it if found.
 
There are three benefits of this.
1) it is less code to reuse a THROW by number rather than by text,
2) I can change the text in one place only for all uses,
3) Internationalisartion is much easier.
 
Stephen

Sorry for the faIled transition to a new machine.

Stephen
--
Stephen Pelc, stephen@vfxforth.com
Wodni & Pelc GmbH
Vienna, Austria
Tel: +44 (0)7803 903612, +34 649 662 974
http://www.vfxforth.com/downloads/VfxCommunity/ - free VFX Forth downloads