From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Evans Winner Newsgroups: gmane.emacs.devel Subject: Re: Document that symbol prefix "my-" (or other) should be left for users Date: Tue, 15 Dec 2015 20:12:48 -0700 Message-ID: <86mvtbf5n3.fsf@gmail.com> References: <87mvtekydf.fsf@mithlond.arda> <87egeqkwj2.fsf@mithlond.arda> <87mvtbinc3.fsf@gnu.org> <18664dc1-aedb-4300-ad9d-d5bc9c363bc5@default> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1450238024 31777 80.91.229.3 (16 Dec 2015 03:53:44 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 16 Dec 2015 03:53:44 +0000 (UTC) To: Emacs developers Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Dec 16 04:53:40 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1a939m-0000rD-Ri for ged-emacs-devel@m.gmane.org; Wed, 16 Dec 2015 04:53:38 +0100 Original-Received: from localhost ([::1]:45228 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a92y6-0002XK-S6 for ged-emacs-devel@m.gmane.org; Tue, 15 Dec 2015 22:41:34 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38434) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a92xk-0002Gt-Gy for emacs-devel@gnu.org; Tue, 15 Dec 2015 22:41:15 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a92tp-0003eq-6q for emacs-devel@gnu.org; Tue, 15 Dec 2015 22:37:12 -0500 Original-Received: from mail-ob0-x22c.google.com ([2607:f8b0:4003:c01::22c]:34315) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a92tp-0003em-28 for emacs-devel@gnu.org; Tue, 15 Dec 2015 22:37:09 -0500 Original-Received: by mail-ob0-x22c.google.com with SMTP id iw8so23401145obc.1 for ; Tue, 15 Dec 2015 19:37:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:references:date:in-reply-to:message-id:user-agent :mime-version:content-type; bh=IRKtbCYont3p1zTyS2ZQ4x54XA6fjNsQzFvM39WdTdQ=; b=CI0xHA2fby0ozvUgklIGdaOiVv0WIe2O7vSU9iSpS1kY47B741u1tXexbEhgIU5mSH QmUj36YdFHuIanE+6MrWWvG9ZPEiB/VcT0iGK3UzuB6Qy0nmmXiuClCzcN1FX++bFpZ8 Y+6lHw2YywBBx6QBPb5v6ilCWi72suERFAc37Cx1JM7loM7cNccBlrPM1+axM+M4Emb/ yBNAhpX2nZEG6Uypi0N5ry25/oiNsEB1IbGBv1XxDkXhgcFMiPwe6JfUGpo0WFm3RY5b 2WBTxsuvaoNwuFNmDvyPjd60RWE2izCFBPvID0TiyezJvRa6MfYPGtTs37KciUQDuHWW P8cg== X-Received: by 10.60.174.130 with SMTP id bs2mr33973873oec.42.1450235571675; Tue, 15 Dec 2015 19:12:51 -0800 (PST) Original-Received: from mongo (c-50-155-171-251.hsd1.co.comcast.net. [50.155.171.251]) by smtp.gmail.com with ESMTPSA id r9sm1850923oih.6.2015.12.15.19.12.50 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 15 Dec 2015 19:12:51 -0800 (PST) In-Reply-To: (John Wiegley's message of "Tue, 15 Dec 2015 12:32:20 -0800") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (windows-nt) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:4003:c01::22c X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:196345 Archived-At: John Wiegley writes: Drew has a point. How about we wait until there's some instance of the problem in the wild that needs us to document such a convention? There's been a lot of time for this to become an issue, and it hasn't yet. For what it's worth, it's happened to me, but a long time ago and I don't remember what function name I stepped on. If it's happened to me, I would guess it's happened to other people. Creating a name clash isn't a bug in Emacs, so why would I (or anyone else) report it? So if it's happening, it might not be something that would come up on the radar here very often. I finally discovered what I'd done and jsut renamed my function. Short of giving Elisp a package system like Common Lisp, it seems that the solution is just to make sure your personal prefix is complex enough that it is unlikely to be duplicated in other people's code.