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: Tue, 07 Nov 2023 06:50:36 +0100 Message-ID: <87fs1ikt77.fsf@dataswamp.org> References: <83r0l32hi1.fsf@gnu.org> <87bkc6ftgq.fsf@dataswamp.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="12870"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) To: emacs-devel@gnu.org Cancel-Lock: sha1:sltMw4W1+x4BjwamhqMaxHII/xo= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Nov 07 12:54:14 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 1r0Ker-00037P-V0 for ged-emacs-devel@m.gmane-mx.org; Tue, 07 Nov 2023 12:54:13 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1r0Ke7-0008K2-Nn; Tue, 07 Nov 2023 06:53:27 -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 1r0EzE-0002r4-HK for emacs-devel@gnu.org; Tue, 07 Nov 2023 00:50:52 -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 1r0EzC-00045f-Dl for emacs-devel@gnu.org; Tue, 07 Nov 2023 00:50:52 -0500 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1r0Ez9-0006Yb-RB for emacs-devel@gnu.org; Tue, 07 Nov 2023 06:50:47 +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: Tue, 07 Nov 2023 06:53:22 -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:312296 Archived-At: tomas wrote: >>> 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? > > You are allowed to do anything. But then, if you complain > that the function calling signature has changed from under > you, the author is allowed to tell you "told you so". > > Seems like a fair deal to me. Yes, but if there is a convention in code, shouldn't one be able to say about some piece of code, "this code sticks to the convention"? Also, saying that something is "internal" or "public" based on a convention - then all the more reason to explain exactly what the convention means - as, in terms of technology, they are both as public, actually? -- underground experts united https://dataswamp.org/~incal