[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Code for cond*
From: |
Po Lu |
Subject: |
Re: Code for cond* |
Date: |
Wed, 24 Jan 2024 20:33:51 +0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Ihor Radchenko <yantar92@posteo.net> writes:
> Po Lu <luangruo@yahoo.com> writes:
>
>> Stefan Kangas <stefankangas@gmail.com> writes:
>>
>>> If it does _not_ come with such a plan, it's slightly better. But then
>>> that begs the question: why add it?
>>
>> Because it will forever free us of such forms as:
>>
>> (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.
- Re: Code for cond*, (continued)
- Re: Code for cond*, Richard Stallman, 2024/01/20
- Re: Code for cond*, Adam Porter, 2024/01/21
- Re: Code for cond*, tomas, 2024/01/22
- Re: Code for cond*, Richard Stallman, 2024/01/23
- Re: Code for cond*, Po Lu, 2024/01/24
- 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 <=
- Re: Code for cond*, Ihor Radchenko, 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*, 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