all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Drew Adams <drew.adams@oracle.com>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: [External] : Re: operations on path lists
Date: Wed, 8 Feb 2023 23:09:26 +0300	[thread overview]
Message-ID: <Y+QBduAxNB6Ut0rI@protected.localdomain> (raw)
In-Reply-To: <SJ0PR10MB54887B26070F397584371C06F3D89@SJ0PR10MB5488.namprd10.prod.outlook.com>

> > Let us look at `when' little:
> > 
> > - you place `when' when you need `nil' as last resort

The above I was thinking 💭, maybe by mistake, that I am answering to
Swedish friend.

> I don't.  I do just the opposite.  I use `when' and `unless' only
> when the code doesn't use/depend on the return value.  (I'm guessing
> that's what you meant by needing nil as a last resort, though they
> always return nil.)

Thanks, I got your thinking, I like when I enter in your mind with
such details, thanks much. What interesting stuff goes on over
thousands of miles of distance.

Yes, I know those return nil. You got my idea, thanks.

> Before Elisp borrowed `when' and `unless' from other Lisps
> (e.g. Common Lisp), the idiom, especially for a single condition,
> was to use `or' in (or condition do-something) instead of `unless',
> and likewise for `and' and `when'.  That that, usually at top level
> in a function body.  I still have some of those `or' sexps, as does
> standard Emacs code.

Okay, I get the history, thanks.

> > - without parenthesis highlighting sometimes it becomes very difficult
> >   to understand what did `if' author intended to say?
> 
> I don't grok that.

With `cond' I can see, usually, what is meant with the condition, as
it is at least to me better structured than `if', as complexity of
code requires me to count parenthesis or be very careful to understand
which expression belong to which part of `if' or some `if` that
follows up. With parenthesis highlighting that is helped better.

> But then, I don't use `if' unless there are both a then and an else
> part.  I take the time to rewrite, yes, as needed, to communicate to
> myself (as reader) just what the code means to do.

Yes, it is good to communicate to oneself over periods of time, I
forgot already what I was doing back in time, sometimes I study my
program to find out what did I mean with it.


-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/



  parent reply	other threads:[~2023-02-08 20:09 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y+QBduAxNB6Ut0rI@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.