From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Zachary Kanfer Newsgroups: gmane.emacs.devel Subject: Re: Proposal to change naming format to allow package-prefix/function-name Date: Mon, 30 Dec 2019 16:50:57 -0500 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000004ba469059af2d7ae" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="210320"; mail-complaints-to="usenet@blaine.gmane.org" Cc: Emacs developers To: Juanma Barranquero Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 30 22:52:01 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1im2xF-000sZV-4F for ged-emacs-devel@m.gmane.org; Mon, 30 Dec 2019 22:52:01 +0100 Original-Received: from localhost ([::1]:36906 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1im2xD-0004IG-H3 for ged-emacs-devel@m.gmane.org; Mon, 30 Dec 2019 16:51:59 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58960) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1im2wS-0003qE-Gg for emacs-devel@gnu.org; Mon, 30 Dec 2019 16:51:13 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1im2wP-0006Hu-UC for emacs-devel@gnu.org; Mon, 30 Dec 2019 16:51:11 -0500 Original-Received: from mail-yb1-xb35.google.com ([2607:f8b0:4864:20::b35]:38697) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1im2wP-0006Ee-KY for emacs-devel@gnu.org; Mon, 30 Dec 2019 16:51:09 -0500 Original-Received: by mail-yb1-xb35.google.com with SMTP id f130so14642743ybb.5 for ; Mon, 30 Dec 2019 13:51:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=IrUzKGJK2Mkm0UtavJHziBgZ6aB1AJt3v134TOTV9GE=; b=XiFE6TvBlBxtjq6HvVe3kQBezZK8M1nO5NOOFdvciMXF0x0XogpmOCMXwI0q+hZzy5 vlFEkwIvsqNacCpTyCoTIUabGeUdkA8lfexkruwVbl0AF71uHoOX+HwYyMbWuqjN8wF9 bvvKdC4siuTrinbA3GL2eBcQpY3mLj/OhNkCe23+Mvq9xNwIrcBSE+J0QL2v0uxOF481 DEbxzm+z2OhtiAuOJNx8bck4nI9xhvQQur8pQ3Oh8+Xqnd0itu5DRNRwKiTPQlvaY0BT EcSN0Lut7nofYQZZVHsvUtZPgXE1aMbktK+f0bFnqHI8sDRRnqAuA7NlMhI4alezpCvM 9y5Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=IrUzKGJK2Mkm0UtavJHziBgZ6aB1AJt3v134TOTV9GE=; b=QVrTxykDb4QoeIFiI3kwZpcE7Bb4oqgznka9jLED2lIgEe2edEUu4lQbP0RnCemKBH qDFGlQK9lQNf/PijUAlKHAhRRGmQsLDpCbmPd/lJCnmiJFL0xGaGIcYgvOUql2PpDsKi qGOrnAQYXOjbTyNlLpzI+btfdEN+iEBT9tEol+ERW5Ai57IcVglOFw5bfkd2eGH+CO6h d2ONXlFPMh9m+8Hga/tQJRKFYH/232QTELv+lDwhN8+bf2Jj5VmMyRSPLE2Z0O38IjeG ZVbdu47VI6eD16jOLYOCb8Kv+4sF4Ivl/lPsny/4a7ONomgC5uJOahSYj2oxbemHIOW5 rxAA== X-Gm-Message-State: APjAAAUYPE4VcygtRAG4Aqa8tOnKyYh2twYflwi572U+rqPLsemA3u25 r7gB1mp7OzpxTeXq2T/FboeFhb1GbUneCTYeAN4= X-Google-Smtp-Source: APXvYqzYAysm73yqS3vPSnmQxaq1KOIapB2BHlQJgAtCXDWWeSWZ0bjazfY6foEdqgYLS6fogAxL6V8+dUHA7R1r3fg= X-Received: by 2002:a25:e08f:: with SMTP id x137mr51718709ybg.497.1577742668373; Mon, 30 Dec 2019 13:51:08 -0800 (PST) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::b35 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:243788 Archived-At: --0000000000004ba469059af2d7ae Content-Type: text/plain; charset="UTF-8" > But if it were, in a Lisp context colon (:) would make more sense IMHO, as it is used in Common Lisp to separate the namespace ("package", in CL-speak) from the symbol name. Perhaps. My gut feeling is that package-prefix/function-name is more readable than package-prefix:function-name, and also more obvious to new users, but I think either would be better than the current dash separation. I would think that any future implementation of namespaces would be able to work with any character chosen here; it wouldn't be just a copy-and-paste of CL code. On Mon, Dec 30, 2019 at 7:04 AM Juanma Barranquero wrote: > > On Mon, Dec 30, 2019 at 8:03 AM Zachary Kanfer wrote: > > > Some Elisp functions that are part of Emacs already follow this format. > > 1. Many eshell functions already follow this format, for example > eshell/ls, eshell/exit, and eshell/define. > > 2. Pcomplete functions use this format, even some for more than one > hierarchical level, e.g. pcomplete/gzip, > pcomplete/erc-mode/complete-command, pcomplete/org-mode/block-option/src. > > 3. Org-plot has half a dozen functions, like org-plot/goto-nearest-table. > > I think this proposal is unlikely to gain traction. But if it were, in a > Lisp context colon (:) would make more sense IMHO, as it is used in Common > Lisp to separate the namespace ("package", in CL-speak) from the symbol > name. That would make easier to adapt to CL-style namespaces, if they were > implemented in Emacs some day (which I think won't ever happen, if previous > discussions on the subject are to be believed). > > > --0000000000004ba469059af2d7ae Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
> But if it were, in a Lisp context colon (:) woul= d make more sense IMHO,=20 as it is used in Common Lisp to separate the namespace ("package"= , in=20 CL-speak) from the symbol name.

Perhaps. My gut fe= eling is that package-prefix/function-name is more readable than package-pr= efix:function-name, and also more obvious to new users, but I think either = would be better than the current dash separation. I would think that any fu= ture implementation of namespaces would be able to work with any character = chosen here; it wouldn't be just a copy-and-paste of CL code.
=

= On Mon, Dec 30, 2019 at 7:04 AM Juanma Barranquero <lekktu@gmail.com> wrote:

On Mon, Dec 30, 2019 = at 8:03 AM Zachary Kanfer <zkanfer@gmail.com> wrote:

> Some Elisp functio= ns that are part of Emacs already follow this format.
> 1. Many eshel= l functions already follow this format, for example eshell/ls, eshell/exit,= and eshell/define.
> 2. Pcomplete functions use this format, even so= me for more than one hierarchical level, e.g. pcomplete/gzip, pcomplete/erc= -mode/complete-command, pcomplete/org-mode/block-option/src.
> 3. Org= -plot has half a dozen functions, like org-plot/goto-nearest-table.

= I think this proposal is unlikely to gain traction. But if it were, in a Li= sp context colon (:) would make more sense IMHO, as it is used in Common Li= sp to separate the namespace ("package", in CL-speak) from the sy= mbol name. That would make easier to adapt to CL-style namespaces, if they = were implemented in Emacs some day (which I think won't ever happen, if= previous discussions on the subject are to be believed).


--0000000000004ba469059af2d7ae--