Hello Damien!
I am not sure I understand the reasoning behind condx: I think cond is already a
macro, which only evaluates a consequent, if the predicate of its case is #t.
Additionally multiple expressions are possible in each branch.
To clarify, I ask: What is the case, where condx does or does
Hello Zelphir,
condx evaluate all code(s) in the 'exec' block until a conditional is true,
it then evaluate the consequent code of course.
So ,yes your true it saves a lot of nesting parenthesis as in this example:
here a code with condx and without it:
(define (ssigma-proto-condx L t)
(set!
On 12.09.2021 19:05, Damien Mattei wrote:
> Hello Zelphir,
>
> condx evaluate all code(s) in the 'exec' block until a conditional is true,
> it then evaluate the consequent code of course.
> So ,yes your true it saves a lot of nesting parenthesis as in this example:
>
Interesting macro. I think
Hi Damien!
I see! Indeed, some indentation happening there. I get the point now, thank you.
Could be well worth it, but it depends on how much you get out of it, compared
to how much additional mental load you get for introducing a new control flow
concept. Sometimes it is worth taking a step back
