Sujet : Re: else ladders practice
De : david.brown (at) *nospam* hesbynett.no (David Brown)
Groupes : comp.lang.cDate : 06. Nov 2024, 08:38:47
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vgf6e7$211ad$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
User-Agent : Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0
On 06/11/2024 00:01, Bart wrote:
On 05/11/2024 20:33, David Brown wrote:
On 05/11/2024 20:39, Waldek Hebisch wrote:
David Brown <david.brown@hesbynett.no> wrote:
On 05/11/2024 13:42, Waldek Hebisch wrote:
Bart <bc@freeuk.com> wrote:
>
Then we disagree on what 'multi-way' select might mean. I think it means
branching, even if notionally, on one-of-N possible code paths.
>
OK.
>
I appreciate this is what Bart means by that phrase, but I don't agree
with it. I'm not sure if that is covered by "OK" or not!
>
You may prefer your own definition, but Bart's is resonable one.
>
The only argument I can make here is that I have not seen "multi-way select" as a defined phrase with a particular established meaning.
Well, it started off as 2-way select, meaning constructs like this:
x = c ? a : b;
x := (c | a | b)
Where one of two branches is evaluated. I extended the latter to N-way select:
x := (n | a, b, c, ... | z)
I appreciate that this is what you have in your language as a "multi-way select". I can see it being a potentially useful construct (though personally I don't like the syntax at all).
The only thing I have disagreed with is your assertions that what you have there is somehow the only "true" or "correct" concept of a "multi-way selection".
else ladders practice
Re: else ladders practice
