unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Paul W. Rankin" <pwr@bydasein.com>
Cc: Emacs-Devel List <emacs-devel@gnu.org>
Subject: Re: declare function/macro private
Date: Mon, 07 Jun 2021 01:59:43 -0400	[thread overview]
Message-ID: <jwvczsyp6k0.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <574D41CF-B2A8-4D4A-A622-B3510F9CBC26@bydasein.com> (Paul W. Rankin's message of "Mon, 07 Jun 2021 14:49:54 +1000")

>> No, I'm still wondering what it is you find to be different.
>> My current guess is that you fear that "--" has currently been used
>> carelessly and imposing a more "structured" meaning to it after the fact
>> will hence introduce problems, whereas your declaration would come right
>> away with an associated "precise" meaning.
> I was *so sure* I had made this clear having said it four times, but okay:
> I do not wish to impose or change anything.

I'm not sure which part of what you quoted made you think that I think
you with to impose or change anything (other than add a new
declaration, obviously).

> An optional addition. That's it. No one forces anyone to use it, just like
> we have the interactive-only declaration and no one's house burnt down.

Of course.  My participation here is just based on the fact that your
suggestion made me think about what we should do with "--".

From that stand point the two discussions are orthogonal.  They only
interact to the extent that they provide similar features so they are
somewhat redundant.

> Trying to retroactively impose some definitive meaning upon people's
> use of "--" is, as I said, the path to ruin.

I disagree.  I've been in the business of slowly changing ELisp coding
style for more than 20 years now, and while I'm not sure that what I've
proposed here to do with "--" would work well, I'm pretty sure it would
not be a path to ruin.

> Others do not necessarily know what I know, i.e. while I may know that "--"
> is a convention that means "internal" in Elisp, other people may not (or
> likely do not). I suspect many programmers use it just because they've seen
> it used in other packages. And given that Elisp does not have any explicit
> definition of what is "internal" it would make little sense to impose one
> now and say "oh well that's what we meant all along".

I think most people who don't know better won't see any difference
either after we'd introduce the new rule.  Or if they do, they'd then
learn about it and either adjust their code or ignore the warning.

> This is not and was never part of my suggestion.

Of course not.  That was my suggestion.


        Stefan




  reply	other threads:[~2021-06-07  5:59 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 [this message]
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
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=jwvczsyp6k0.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=pwr@bydasein.com \
    /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).