From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: master 48ac40e60e: ; Fix last change.
Date: Sun, 14 Aug 2022 22:15:28 +0300 [thread overview]
Message-ID: <83wnbaiqlr.fsf@gnu.org> (raw)
In-Reply-To: <87k07afycf.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun, 14 Aug 2022 20:56:32 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
> Date: Sun, 14 Aug 2022 20:56:32 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Sorry, I reject the idea that abstract classes cannot be usefully
> > documented in concrete terms. At least there's no excuse for not
> > trying.
>
> I think it's much easier to describe what the function does in the
> semi-negative: The argument is a function, and it's not a
> lambda/closure.
It might be easier, but I personally would remain utterly confused by
such a description.
In general, saying what a thing is NOT is a very inefficient method of
explaining what it IS, because there are so many things that are not
it.
What exactly is the problem with the current wording? Can you or
Stefan or someone else point out the actual deficiencies (as opposed
to semi-philosophical considerations)?
next prev parent reply other threads:[~2022-08-14 19:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166049949398.16955.13217655219158269477@vcs2.savannah.gnu.org>
[not found] ` <20220814175134.47827C09BFD@vcs2.savannah.gnu.org>
2022-08-14 18:16 ` master 48ac40e60e: ; Fix last change Stefan Monnier
2022-08-14 18:31 ` Eli Zaretskii
2022-08-14 18:42 ` Stefan Monnier
2022-08-14 18:46 ` Eli Zaretskii
2022-08-14 18:56 ` Lars Ingebrigtsen
2022-08-14 19:15 ` Eli Zaretskii [this message]
2022-08-14 19:23 ` Lars Ingebrigtsen
2022-08-15 2:23 ` Eli Zaretskii
2022-08-15 4:30 ` Lars Ingebrigtsen
2022-08-15 11:30 ` Eli Zaretskii
2022-08-15 2:37 ` Stefan Monnier
2022-08-15 11:20 ` Eli Zaretskii
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=83wnbaiqlr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).