[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Code for cond* - cond*-match, cond*-subpat and backtrack-aliases
From: |
Richard Stallman |
Subject: |
Re: Code for cond* - cond*-match, cond*-subpat and backtrack-aliases |
Date: |
Wed, 31 Jan 2024 22:51:55 -0500 |
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> I wonder why (bind*) evaluates only its first value to determine
> if the binding condition is true? We already have macros which
> evaluate the "truth of a set of bindings": the members of the
> if-let family. And they
> "Evaluate each binding in turn, as in ‘let*’, stopping if a
> binding value is nil. If all are non-nil return the [final]
> value."
That does not seem natural to me at all. I don't see that it is
better.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
- Re: Code for cond*, (continued)
Re: Code for cond*, Alan Mackenzie, 2024/01/24
- Re: Code for cond*, Emanuel Berg, 2024/01/24
- Re: Code for cond*, Manuel Giraud, 2024/01/24
- Re: Code for cond* - cond*-match, cond*-subpat and backtrack-aliases, Alan Mackenzie, 2024/01/25
- Re: Code for cond* - cond*-match, cond*-subpat and backtrack-aliases, Richard Stallman, 2024/01/28
- Re: Code for cond* - cond*-match, cond*-subpat and backtrack-aliases, JD Smith, 2024/01/29
- Re: Code for cond* - cond*-match, cond*-subpat and backtrack-aliases,
Richard Stallman <=