unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: help-gnu-emacs@gnu.org
Subject: Re: [External] : Re: operations on path lists
Date: Wed, 8 Feb 2023 01:39:57 +0300	[thread overview]
Message-ID: <Y+LTPZBJvUOAbiP8@protected.localdomain> (raw)
In-Reply-To: <87k00xje04.fsf@dataswamp.org>

* Emanuel Berg <incal@dataswamp.org> [2023-02-05 16:16]:
> The reader ... you, the writer, should write as good code as
> possible, that will benefit everyone the same way.

OK sure, but where is the definition of "as good code as possible"?

It is opinionated.

Every person, so I expect, strives to write "as good code as
possible".

Let us look at `when' little:

- you place `when' when you need `nil' as last resort

- what if you change your mind in future and wish to modify function
  to return "" as last resort? You will need to introduce `if`
  function, you have to restructure it. You have to remove `when' and
  replace with something else.

- without parenthesis highlighting sometimes it becomes very difficult
  to understand what did `if' author intended to say? 

- multiple `if' statements one ofter other do not look nice and
  readable, and I have to use

- if you use `cond', you remain with `cond', but only change nil to ""

Some people write long functions, if, then, when, it is not nicely
indented, restructuring is difficult, what did author want to say?
Hard to think of 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-07 22:39 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 [this message]
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=Y+LTPZBJvUOAbiP8@protected.localdomain \
    --to=bugs@gnu.support \
    --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.
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).