Re: THROW codes and ambiguous conditions

On 8/06/2025 9:51 pm, albert@spenarnc.xs4all.nl wrote:

In article <2025Jun8.095626@mips.complang.tuwien.ac.at>,
Anton Ertl <anton@mips.complang.tuwien.ac.at> wrote:

albert@spenarnc.xs4all.nl writes:

>
It is occasionally useful to have conversions to a string that
not immediately prints. Even figforth had a (D.R) that was a
D.R without the type.

>
It's not in the fig-Forth Installation Manual / Glossary / Model Release !
>
http://wiki.yak.net/1089/fig-FORTH_Manuals_May79.pdf
>
nor in the source code.
>
https://raw.githubusercontent.com/ForthHub/FIG-Forth/refs/heads/master/fig.fth

 
I should have known better.
https://home.hccnet.nl/a.w.m.van.der.horst/figdoc.zip
I remembered the way D. was reduced in the code to
D.R and confused the two mechanisms.

It's probably easier to justify (D.) than (D.R).  If one needs to right-justify
numbers, chances are one will need to right-justify non-numeric strings as well.
For this reason I have S.R in the kernel and (S.R) as a library function.