unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Boruch Baum <boruch_baum@gmx.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 0278C47F-42CE-45C4-B789-83C57DF1A191@bydasein.com,
	monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: declare function/macro private
Date: Mon, 7 Jun 2021 21:14:56 -0400	[thread overview]
Message-ID: <20210608011456.zc56i2i22tboxcgf@E15-2016.optimum.net> (raw)
In-Reply-To: <835yyphmqx.fsf@gnu.org>

On 2021-06-07 15:39, Eli Zaretskii wrote:
> > Date: Sun, 6 Jun 2021 23:35:26 -0400
> > From: Boruch Baum <boruch_baum@gmx.com>
> > Cc: "Paul W. Rankin" <0278C47F-42CE-45C4-B789-83C57DF1A191@bydasein.com>,
> >  Stefan Monnier <monnier@iro.umontreal.ca>
> >
> > On Sun, 06 Jun 2021 22:54:41 -0400, Stefan Monnier wrote:
> >
> > > My current guess is that you fear that "--" has currently been used
> > > carelessly
> >
> > Using 'ivy/counsel' and performing M-x -- gives me 56 completion
> > candidates. 23 are from magit, Here are the rest:
>
> You need to remove from this list those which are intended for
> invocation via the mouse.  They aren't relevant to the issue at hand,
> because the "--" was used there "for other purposes".

The point was just to support Paul Rankin's position that a '--'
substring isn't a reliable determinant of a function's public/private
nature, so can't be used as an alternative to an explicit (optional)
declaration.

My concern isn't the declaration, but the scope of its consequences. For
example, an emacs user who does no elisp programming would be happy to
have no private variable/function results appear among completion
candidates when performing M-x describe-variable/function. Elisp
programmers would want those completion candidates exposed, and subject
to being extended/advised.

--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1  7286 0036 9E45 1595 8BC0



  reply	other threads:[~2021-06-08  1:14 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07  3:35 declare function/macro private Boruch Baum
2021-06-07  4:49 ` Paul W. Rankin via Emacs development discussions.
2021-06-07  5:59   ` Stefan Monnier
2021-06-07  6:45     ` Paul W. Rankin via Emacs development discussions.
2021-06-07 12:39 ` Eli Zaretskii
2021-06-08  1:14   ` Boruch Baum [this message]
2021-06-08  4:20     ` Arthur Miller
2021-06-08  5:49       ` tomas
2021-06-08 15:46     ` Stefan Monnier
  -- strict thread matches above, loose matches on Subject: below --
2021-06-06  4:27 Paul W. Rankin via Emacs development discussions.
2021-06-06  7:09 ` Omar Polo
2021-06-06  7:18   ` Paul W. Rankin via Emacs development discussions.
2021-06-06  9:53 ` Lars Ingebrigtsen
2021-06-06 12:43   ` Paul W. Rankin via Emacs development discussions.
2021-06-08  9:43     ` Lars Ingebrigtsen
2021-06-08 17:26       ` Robin Tarsiger
2021-06-06 18:05 ` Stefan Monnier
2021-06-06 18:12   ` Tassilo Horn
2021-06-06 20:12     ` Stefan Monnier
2021-06-07  0:51       ` Paul W. Rankin via Emacs development discussions.
2021-06-07  1:37         ` Arthur Miller
2021-06-07  1:43           ` Paul W. Rankin via Emacs development discussions.
2021-06-07 13:38             ` Arthur Miller
2021-06-07  0:59   ` Paul W. Rankin via Emacs development discussions.
2021-06-07  2:54     ` Stefan Monnier
2021-06-07 18:24       ` Arthur Miller

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=20210608011456.zc56i2i22tboxcgf@E15-2016.optimum.net \
    --to=boruch_baum@gmx.com \
    --cc=0278C47F-42CE-45C4-B789-83C57DF1A191@bydasein.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.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).