From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Imports / inclusion of s.el into Emacs Date: Tue, 05 May 2020 13:23:31 -0400 Message-ID: References: <0c88192c-3c33-46ed-95cb-b4c6928016e3@default> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="121813"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Richard Stallman , Emacs developers , =?utf-8?B?Sm/Do28gVMOhdm9yYQ==?= , =?utf-8?B?7KGw7ISx67mI?= , Eli Zaretskii , Drew Adams To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue May 05 19:24:34 2020 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 1jW1J4-000VXr-Ds for ged-emacs-devel@m.gmane-mx.org; Tue, 05 May 2020 19:24:34 +0200 Original-Received: from localhost ([::1]:55026 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jW1J3-0001Kq-Gs for ged-emacs-devel@m.gmane-mx.org; Tue, 05 May 2020 13:24:33 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41408) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jW1IA-0000Sw-SI for emacs-devel@gnu.org; Tue, 05 May 2020 13:23:38 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:46409) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jW1I8-0002HO-8K; Tue, 05 May 2020 13:23:38 -0400 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 4D63081246; Tue, 5 May 2020 13:23:34 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 956EA805BA; Tue, 5 May 2020 13:23:32 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1588699412; bh=9gymp3O7Mt4ryE4lKd3xxMnbiMDwjy7cDhStG35zALg=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=VWgnxtlKMovXA8/mCXO0zw3Hpra6glJA85HNKezM9RfxyFTsA7obABAn+9WkEzrjN lVUrcIuDTe+dSoeGDsLOjIQu/ypcHzQXoulq4cagPuna2bh07SeLomBRe7r6nwpXar NsmBPPafib0Qqj0kEPan02M/8JD94hAOqubcUbrvsk5mYYOGK4d29ZeVYZYrNgBCSd etQ5DNAkKoBRx1fxXklPyjqcROu89ltwosNx3bMfJeqOfsiLPG/JnvIc+DiGyQGrqj vxImMgSjXPvKXhQclrFaD/8OntCVtXO8rxf3SIp9l2c2OJ1Yg8oMVAYG5t23LNSTWh jmjkiUmhtgurg== Original-Received: from alfajor (unknown [216.154.3.202]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 37ECB12028A; Tue, 5 May 2020 13:23:32 -0400 (EDT) In-Reply-To: (Dmitry Gutov's message of "Tue, 5 May 2020 15:22:48 +0300") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-detected-operating-system: by eggs.gnu.org: First seen = 2020/05/05 13:23:34 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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" Xref: news.gmane.io gmane.emacs.devel:249016 Archived-At: >> You'll always >> get a group of people that really expected it to be multibyte-string and >> group of people that expect string-multibyte. > If there is an actual naming standard, the people can learn. There is a naming standard that every Elisp programmer must learn, it's the use of a namespace prefix to group elements. Sadly, this standard is only taken half-seriously for non-core Elisp definitions. Of course that standard doesn't say on what basis to group. But currently, if you look at the "string-" and "multibyte-" prefixes, it's immediately clear that "multibyte-" has not been really used as a namespace prefix whereas "string-" has been used as a namespace prefix for several function (for some function it's been used as a namespace prefix but not all, e.g. `string-rectangle`). Which is why I propose to rename `multibyte-string-p` to `string-multibyte-p`, since it would feel at home inside the "string" group. Then Elisp programmers would benefit from the naming convention for that function as well. Stefan