From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Emanuel Berg Newsgroups: gmane.emacs.devel Subject: Re: seq.el and the complexity of Emacs Lisp. Date: Mon, 06 Nov 2023 22:43:49 +0100 Message-ID: <87bkc6ftgq.fsf@dataswamp.org> References: <83r0l32hi1.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40834"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) To: emacs-devel@gnu.org Cancel-Lock: sha1:wwqrVtCboIWEnXAQeD3AwIal9rc= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Nov 07 04:22:04 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1r0CfD-000AQY-Fc for ged-emacs-devel@m.gmane-mx.org; Tue, 07 Nov 2023 04:22:03 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1r0Cek-0004D4-WB; Mon, 06 Nov 2023 22:21:35 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r07O5-0000LY-Df for emacs-devel@gnu.org; Mon, 06 Nov 2023 16:44:01 -0500 Original-Received: from ciao.gmane.io ([116.202.254.214]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r07O3-0002Ju-ON for emacs-devel@gnu.org; Mon, 06 Nov 2023 16:44:01 -0500 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1r07O0-0009vh-NP for emacs-devel@gnu.org; Mon, 06 Nov 2023 22:43:57 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Mail-Copies-To: never Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Mon, 06 Nov 2023 22:21:33 -0500 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:312281 Archived-At: 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? Even as it is actually available everywhere, just like any some-public-function defined? To what extent has this convention been upheld in the Emacs source? Maybe the byte-compiler should warn when such functions are used from elsewhere? But maybe then people would just rename them with a single dash instead of two? But that, by all means, at least would uphold the convention. -- underground experts united https://dataswamp.org/~incal