[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Installing cond* in core
From: |
Stefan Monnier |
Subject: |
Re: Installing cond* in core |
Date: |
Tue, 12 Mar 2024 23:05:51 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
> > > But there are also nonempty ni-exit clauses:
> > >
> > > > (cond*
> > > > (:no-exit (match* PAT FORM) THEN)
> > > > . ALWAYS)
> > >
> > > Can rewriting handle that?
>
> > Assuming it means "if PAT matches, execute THEN (with the corresponding
> > bindings) for its side effects, and in all cases continue with ALWAYS
> > without PAT's bindings", then it's just
>
> The bindings cover both THEN and ALWAYS.
Then I don't understand what's the intended semantics: how can you use
PAT's bindings over ALWAYS when PAT failed to match?
Stefan
- Re: Installing cond* in core, Richard Stallman, 2024/03/12
- Re: Installing cond* in core,
Stefan Monnier <=
- Re: Installing cond* in core, Richard Stallman, 2024/03/15
- Re: Installing cond* in core, Stefan Monnier, 2024/03/16
- Re: Installing cond* in core, Richard Stallman, 2024/03/17
- Re: Installing cond* in core, Stefan Monnier, 2024/03/17
- Re: Installing cond* in core, Peter Hull, 2024/03/19
- Re: Installing cond* in core, Richard Stallman, 2024/03/20
- Re: Installing cond* in core, Stefan Monnier, 2024/03/20