From: Emanuel Berg <incal@dataswamp.org>
To: emacs-devel@gnu.org
Subject: Re: seq.el and the complexity of Emacs Lisp.
Date: Tue, 07 Nov 2023 13:26:29 +0100 [thread overview]
Message-ID: <87wmutkave.fsf@dataswamp.org> (raw)
In-Reply-To: 835y2d3hco.fsf@gnu.org
Eli Zaretskii wrote:
>>>> I looked at seq.el to try to get an idea what those
>>>> functions do. It was difficult to get this from the doc
>>>> strings, because it wasn't explicitly stated which ones
>>>> are for users and which ones are internal.
>>>
>>> Our convention nowadays is that any function/variable that
>>> has 2 dashes after the prefix, in this case
>>> seq--SOMETHING, is internal, and all the others
>>> are public.
>>
>> Are you only allowed to use some--private-function in the
>> same file where it is defined?
>
> That's the convention, yes.
Maybe the byte-compiler should warn when using such functions
in/from other files?
>> To what extent has this convention been upheld in the
>> Emacs source?
>
> It is upheld quite closely.
Okay, great!
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2023-11-07 12:26 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 8:21 What's missing in ELisp that makes, people want to use cl-lib? Pedro Andres Aranda Gutierrez
2023-11-03 9:27 ` João Távora
2023-11-03 10:43 ` Pedro Andres Aranda Gutierrez
2023-11-03 13:37 ` Gerd Möllmann
2023-11-03 14:27 ` Eli Zaretskii
2023-11-03 15:08 ` Gerd Möllmann
2023-11-03 15:13 ` Eli Zaretskii
2023-11-03 15:30 ` Gerd Möllmann
2023-11-03 15:39 ` Eli Zaretskii
2023-11-03 15:49 ` Gerd Möllmann
2023-11-06 2:27 ` seq.el and the complexity of Emacs Lisp Richard Stallman
2023-11-06 6:51 ` Philip Kaludercic
2023-11-06 7:16 ` Gerd Möllmann
2023-11-07 10:24 ` João Távora
2023-11-09 21:02 ` Jim Porter
2023-11-09 21:20 ` João Távora
2023-11-09 23:49 ` Jim Porter
2023-11-09 23:53 ` Jim Porter
2023-11-10 2:31 ` João Távora
2023-11-10 3:27 ` Jim Porter
2023-11-10 10:03 ` Alan Mackenzie
2023-11-10 12:01 ` Eli Zaretskii
2023-11-10 10:13 ` Michael Heerdegen
2023-11-10 10:26 ` João Távora
2023-11-10 13:30 ` Michael Heerdegen
2023-11-08 3:08 ` Richard Stallman
2023-11-08 3:08 ` Richard Stallman
2023-11-08 5:31 ` Gerd Möllmann
2023-11-06 8:11 ` Björn Bidar
2023-11-06 12:28 ` Eli Zaretskii
2023-11-06 21:43 ` Emanuel Berg
2023-11-07 5:21 ` tomas
2023-11-07 5:50 ` Emanuel Berg
2023-11-07 6:21 ` Emanuel Berg
2023-11-07 12:02 ` Ihor Radchenko
2023-11-07 12:28 ` Emanuel Berg
2023-11-07 12:20 ` Eli Zaretskii
2023-11-07 12:29 ` Emanuel Berg
2023-11-07 11:58 ` Eli Zaretskii
2023-11-07 12:26 ` Emanuel Berg [this message]
2023-11-08 3:08 ` Richard Stallman
[not found] ` <874jhz9u8z.fsf@>
2023-11-06 12:35 ` Eli Zaretskii
2023-11-06 12:50 ` Björn Bidar
2023-11-06 21:30 ` Emanuel Berg
2023-11-07 7:35 ` Harald Judt
2023-11-07 10:14 ` Emanuel Berg
2023-11-07 12:26 ` Harald Judt
2023-11-07 12:38 ` Ihor Radchenko
2023-11-07 12:58 ` Eli Zaretskii
2023-11-07 13:50 ` Emanuel Berg
2023-11-07 14:12 ` 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=87wmutkave.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--cc=emacs-devel@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 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).