[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: seq.el and the complexity of Emacs Lisp.
From: |
Emanuel Berg |
Subject: |
Re: seq.el and the complexity of Emacs Lisp. |
Date: |
Tue, 07 Nov 2023 13:26:29 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
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
- Re: seq.el and the complexity of Emacs Lisp., (continued)
- Re: seq.el and the complexity of Emacs Lisp., Eli Zaretskii, 2023/11/06
- Re: seq.el and the complexity of Emacs Lisp., Emanuel Berg, 2023/11/06
- Re: seq.el and the complexity of Emacs Lisp., tomas, 2023/11/07
- Re: seq.el and the complexity of Emacs Lisp., Emanuel Berg, 2023/11/07
- Re: seq.el and the complexity of Emacs Lisp., Emanuel Berg, 2023/11/07
- Re: seq.el and the complexity of Emacs Lisp., Ihor Radchenko, 2023/11/07
- Re: seq.el and the complexity of Emacs Lisp., Emanuel Berg, 2023/11/07
- Re: seq.el and the complexity of Emacs Lisp., Eli Zaretskii, 2023/11/07
- Re: seq.el and the complexity of Emacs Lisp., Emanuel Berg, 2023/11/07
- Re: seq.el and the complexity of Emacs Lisp., Eli Zaretskii, 2023/11/07
- Re: seq.el and the complexity of Emacs Lisp.,
Emanuel Berg <=
- Re: seq.el and the complexity of Emacs Lisp., Richard Stallman, 2023/11/07