----------------------------------------------------------------------------------
@MSGID: 1@dont-email.me> 31f00bd5
@REPLY: <20230923110933.5cc36e51@t530> fcdd022e
@REPLYADDR dxf <dxforth@gmail.com>
@REPLYTO 2:5075/128 dxf
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID: 1@dont-email.me>
@RFC-References: 1@dont-email.me>
<20230923110933.5cc36e51@t530>
@TZUTC: 1000
@PID: Mozilla Thunderbird
@TID: FIDOGATE-5.12-ge4e8b94
On 23/09/2023 8:09 pm, jan Coombs wrote:
> On Sat, 23 Sep 2023 19:33:05 +1000
> dxf <
dxforth@gmail.com> wrote:
>
>> So what shall we do with ANS CASE :)
>
> Ideally, ignore if you do not need CASE, else
> conform with ANS, else use a different name.
I suspect most find `case` too useful to ignore. I provide
ANS as a compatibility add-on.
Mostly OF suffices (applying the don`t use ELSE paradigm).
Should I need a common-exit case, I have is COND CONT.
From the latter I define the compatibility words:
AKA COND CASE
AKA ELSE ENDOF
: ENDCASE POSTPONE DROP POSTPONE CONT ; IMMEDIATE
--- Mozilla Thunderbird
* Origin: A noiseless patient Spider (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5058/104 5075/128
@PATH: 5075/128 5020/1042 4441