Sujet : Re: Why dial-a-standard is not a thing in Forth
De : sjack (at) *nospam* dontemail.me (sjack)
Groupes : comp.lang.forthDate : 20. Apr 2025, 14:25:20
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vu2sk0$3sr9q$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11
User-Agent : tin/2.6.4-20240224 ("Banff") (Linux/6.8.0-58-generic (x86_64))
dxf <
dxforth@gmail.com> wrote:
Really annoying was LMI which on error switched to DECIMAL ...
Someone here awhile back posted modifying LOAD and LIST to convert
the TOS number to decimal regardless of current BASE setting.
Gave it a try and found it indeed helpful.
I'm currently using many vocabularies and my main vocabulary is TOAD and
often I'm working in vocabulary WRK . I kept ABORT to reset vocabulary
to FORTH as well as setting BASE to decimal but it doesn't do
EMPTY-BUFFERS (however that is done on an abort signal from the OS).
Not too annoying since I'm well aware of what to expect on error so
my automatic response to an error is TOAD WRK . The above changes
to LOAD and LIST also help along with a quick status word double-dot
'..' that displays CONTEXT CURRENT BASE LATEST and data stack.
Also have a switch to replace ABORT with an abort in (ABORT) that
doesn't reset vocabulary, base nor clear data stack.
Had setup that split the display with a status line on the display
bottom where data stack status (dots), error and user messages where
shown after every command run. Don't use anymore, no need to be that
fancy.
Not a language issue but a matter of application. These things don't
go into production word definitions but pertain to operations.
I'm sure everyone has his pet setup to help suppress frustrations.
-- me