From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: can `shuffle-vector' be moved? Date: Fri, 13 May 2011 12:26:34 -0300 Message-ID: References: <87pqnny9lk.fsf@lifelogs.com> <87fwojw91r.fsf@lifelogs.com> <87aaeqy7u8.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1305300410 16042 80.91.229.12 (13 May 2011 15:26:50 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 13 May 2011 15:26:50 +0000 (UTC) Cc: emacs-devel@gnu.org To: Ted Zlatanov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 13 17:26:46 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QKuGL-0004oF-P5 for ged-emacs-devel@m.gmane.org; Fri, 13 May 2011 17:26:45 +0200 Original-Received: from localhost ([::1]:42452 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QKuGL-0007IT-5P for ged-emacs-devel@m.gmane.org; Fri, 13 May 2011 11:26:45 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:54883) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QKuGI-0007IO-Fn for emacs-devel@gnu.org; Fri, 13 May 2011 11:26:43 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QKuGH-0002EB-IR for emacs-devel@gnu.org; Fri, 13 May 2011 11:26:42 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]:45911) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QKuGH-0002E7-Fi for emacs-devel@gnu.org; Fri, 13 May 2011 11:26:41 -0400 Original-Received: from 213-159-126-200.fibertel.com.ar ([200.126.159.213]:41734 helo=ceviche.home) by fencepost.gnu.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1QKuGH-0005GW-1O; Fri, 13 May 2011 11:26:41 -0400 Original-Received: by ceviche.home (Postfix, from userid 20848) id DB7F866152; Fri, 13 May 2011 12:26:34 -0300 (ART) In-Reply-To: <87aaeqy7u8.fsf@lifelogs.com> (Ted Zlatanov's message of "Fri, 13 May 2011 09:48:47 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 140.186.70.10 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:139360 Archived-At: KR> ;; These are extensions to Emacs Lisp that provide a degree of KR> ;; Common Lisp compatibility, beyond what is already built-in KR> ;; in Emacs Lisp. > OK. Can there be a cl-macs-extras.el for "general cl-macs based code > that is safe to include in ELisp code"? I really have no idea why you want it in cl-macs: 1- the "macs" part refers to "macros", your function isn't one. 2- it does not provide a CL-style function. 3- using a CL macro in its definition is a property share by a lot more code than just the CL code. And actually, the cl*.el files tend not to use CL features, to avoid circular dependencies. SM> I really meant "similar": if no other code uses this functionality, SM> advertising its existence is not going to increase its use. > I also see lisp/calc/calc-comb.el:math-shuffle-list but you're right, > it's not commonly needed. I still don't think it belongs in cookie1.el, > if only because the name is general and not library-specific, It should probably be called cookie-shuffle-vector, indeed. > but that's an inconsistency all the cookie1.el functions have. The only other function I see in cookie1.el that does not use the "cookie-" prefix is "read-cookie", which is borderline acceptable (we have a few such "shared prefixes" like "turn-on-"). So, `shuffle-vector' does indeed stand out. And the fact that it's autoloaded is a clear sign it is intended to be used by other packages. But I see no good place to put it right now, and I don't think it deserves creating a "misc-lib.el" for itself (although some of the functions in subr.el might be good candidates for such a new package). Stefan