From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Nicolas Petton Newsgroups: gmane.emacs.devel Subject: Re: sequence manipulation functions Date: Wed, 05 Nov 2014 18:41:12 +0100 Message-ID: <874mudilzb.fsf@gmail.com> References: <87oasmmwzt.fsf@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1415209308 1507 80.91.229.3 (5 Nov 2014 17:41:48 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 5 Nov 2014 17:41:48 +0000 (UTC) Cc: Stefan Monnier , Emacs developers To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Nov 05 18:41:43 2014 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 1Xm4aT-0004rL-6Y for ged-emacs-devel@m.gmane.org; Wed, 05 Nov 2014 18:41:41 +0100 Original-Received: from localhost ([::1]:47851 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xm4aS-0001O1-RW for ged-emacs-devel@m.gmane.org; Wed, 05 Nov 2014 12:41:40 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38596) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xm4aA-0001NP-FR for emacs-devel@gnu.org; Wed, 05 Nov 2014 12:41:26 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xm4a5-0005k7-R2 for emacs-devel@gnu.org; Wed, 05 Nov 2014 12:41:22 -0500 Original-Received: from mail-la0-x230.google.com ([2a00:1450:4010:c03::230]:51406) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xm4a5-0005k0-GN for emacs-devel@gnu.org; Wed, 05 Nov 2014 12:41:17 -0500 Original-Received: by mail-la0-f48.google.com with SMTP id gq15so1159939lab.35 for ; Wed, 05 Nov 2014 09:41:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:user-agent:from:to:cc:subject:in-reply-to:date :message-id:mime-version:content-type; bh=OM6F8hVDS+Yrma4qbpVGMu1RrgxEoBN7XL9D3D0/DOc=; b=G+AI14lpj8+hzELQjwfsPLV0wI3kaTwaXKY3vyzRPEvbZ51mh7QiYgrWdc+gjNbB+1 fHwlrKZqVFexmDlmhjpQv4NiFA3oUkzJL3zIjUMjbYlGBsxyor88CE5WxSJUnV2w9tYn 4mA4YzCZN2i9Slp6tvVdpkK16Q3fy9a/ZwY0artxkqvW6C8pyvgM4sEcTKrxM1DgJm/Z 2wEQqjOtKPQ4czu8UVOtDuI9AcXLu5hY6UJv94lMFUL7Eo1T0gtf/6Kit3Y5xvkqNDj0 qaog1QYuVAP01utBQUxS1hU+GhV0f6/h8ZQtRAE7owvnEyIUEaCiiAwclfUkM3xQolQ3 Tbbw== X-Received: by 10.112.25.73 with SMTP id a9mr70617212lbg.10.1415209275824; Wed, 05 Nov 2014 09:41:15 -0800 (PST) Original-Received: from blueberry (31-211-216-84.customers.ownit.se. [31.211.216.84]) by mx.google.com with ESMTPSA id sd10sm1562065lbb.8.2014.11.05.09.41.14 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 05 Nov 2014 09:41:15 -0800 (PST) User-agent: mu4e 0.9.9.6pre3; emacs 24.3.1 In-reply-to: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c03::230 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:176420 Archived-At: I see "cl-lib" as a compatibility package with Common Lisp, not a base library of the language. My goal is not to remove or replace "cl-lib", but to add core sequence functions to Elisp. Nico Drew Adams writes: >> I think these should use a "seq-" prefix. This will not only avoid >> naming conflicts, but also helps discover those functions, since you >> can type `(seq- TAB' to see all related functions. > > No. Emacs should follow Common Lisp in this regard. > http://www.cs.cmu.edu/Groups/AI/html/cltl/clm/node141.html#SECTION001800000000000000000 > > And it should follow it not only in terms of names but also in terms > of behavior, as much as is practical. E.g., `some-p' should be `some', > and it should have the Common Lisp `some' behavior. > > This might already be more or less the case for `cl-some' etc., in > which case there is no need (and it would be a nuisance) to add a > separate `some-p' etc. with a different behavior. -- Nicolas Petton http://nicolas-petton.fr