[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Code for cond*
From: |
Ihor Radchenko |
Subject: |
Re: Code for cond* |
Date: |
Wed, 24 Jan 2024 13:34:22 +0000 |
Po Lu <luangruo@yahoo.com> writes:
>>> (let (x y z)
>>> (cond ((eq (setq x ...) 'bar)
>>> yyy)
>>> ((setq y (... x))
>>> zzz)
>>> ...and so on
>>>
>>> This alone is too important a feature to be consigned to ELPA.
>>
>> May you elaborate how cond* helps simplifying the above example?
>
> It will be possible for a clause to bind variables accessible in
> subsequent ones, eliminating the let and setq forms.
The problem is that cond* is doing much more than just introducing
fall-through bindings.
If we just need fall-through bindings, I'd argue that we should better
introduce them separately; maybe even as a part of the normal `cond'.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
- Re: Code for cond*, (continued)
- Re: Code for cond*, Stefan Kangas, 2024/01/24
- Re: Code for cond*, João Távora, 2024/01/24
- Re: Code for cond*, João Távora, 2024/01/24
- Re: Code for cond*, Po Lu, 2024/01/24
- Re: Code for cond*, Ihor Radchenko, 2024/01/24
- Re: Code for cond*, Po Lu, 2024/01/24
- Re: Code for cond*,
Ihor Radchenko <=
- Re: Code for cond*, João Távora, 2024/01/24
- Re: Code for cond*, Po Lu, 2024/01/24
- Re: Code for cond*, Richard Stallman, 2024/01/26
- Re: Code for cond*, Richard Stallman, 2024/01/26
- Re: Code for cond*, Po Lu, 2024/01/24
- Re: Code for cond*, Ihor Radchenko, 2024/01/24
- Re: Code for cond*, Po Lu, 2024/01/24
- Re: Code for cond*, Ihor Radchenko, 2024/01/24
- Re: Code for cond*, João Távora, 2024/01/24
- Re: Code for cond*, Emanuel Berg, 2024/01/24