From: Jean Louis <bugs@gnu.support>
To: Drew Adams <drew.adams@oracle.com>
Cc: Emanuel Berg <incal@dataswamp.org>,
"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: [External] : Re: operations on path lists
Date: Sat, 4 Feb 2023 21:32:10 +0300 [thread overview]
Message-ID: <Y96kqolQQnzQ4ot/@protected.localdomain> (raw)
In-Reply-To: <SJ0PR10MB5488223CBC059FD1EDC6ADA0F3D49@SJ0PR10MB5488.namprd10.prod.outlook.com>
* Drew Adams <drew.adams@oracle.com> [2023-02-04 20:23]:
> > > (cond ((file-directory-p file) (expand-file-name file))
> > > (t nil))
> >
> > (when (file-directory-p file) (expand-file-name file) )
>
> (and (file-directory-p file) (expand-file-name file))
>
> Use `when' when the return value isn't important.
> Helps human readers.
I understand the idea, and I found `cond' serves that purpose better.
So I follow the same purpose in the essence.
In that particular example, the return value would be rather hidden
and implied from `when'.
For me that is not same as when the value is visible, such as `nil'.
So those are differences in view points on what is helpful to human
reader or not.
If reader is familiar with `when' and not with `cond' it will be
easier, but if readier is familiar with `cond' maybe that is easier.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2023-02-04 18:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 5:32 operations on path lists Samuel Wales
2023-02-04 6:32 ` Jean Louis
2023-02-04 8:06 ` Emanuel Berg
2023-02-04 17:21 ` [External] : " Drew Adams
2023-02-04 18:32 ` Jean Louis [this message]
2023-02-04 21:51 ` Emanuel Berg
2023-02-07 8:34 ` Jean Louis
2023-02-07 10:26 ` Emanuel Berg
2023-02-07 22:39 ` Jean Louis
2023-02-08 2:48 ` Drew Adams
2023-02-08 18:46 ` Drew Adams
2023-02-08 20:09 ` Jean Louis
2023-02-04 18:28 ` Jean Louis
2023-02-04 21:41 ` Emanuel Berg
2023-02-07 8:33 ` Jean Louis
2023-02-07 10:30 ` Emanuel Berg
2023-02-07 14:55 ` [External] : " Drew Adams
2023-02-07 14:55 ` Drew Adams
2023-02-04 21:44 ` Samuel Wales
2023-02-04 21:49 ` Samuel Wales
2023-02-04 14:59 ` Emanuel Berg
2023-02-07 7:35 ` Jean Louis
2023-02-07 10:27 ` Emanuel Berg
2023-02-11 8:18 ` James Thomas
2023-02-11 14:02 ` Ruijie Yu via Users list for the GNU Emacs text editor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y96kqolQQnzQ4ot/@protected.localdomain \
--to=bugs@gnu.support \
--cc=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=incal@dataswamp.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).