From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ilya Shlyakhter Newsgroups: gmane.emacs.devel Subject: Re: CL package suggestion Date: Mon, 9 Apr 2012 12:45:03 -0400 Message-ID: References: <27y5qciwgd.fsf@fencepost.gnu.org> <9lty10iwdr.fsf@fencepost.gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=20cf303f6d6856d50204bd41baf5 X-Trace: dough.gmane.org 1333989916 11092 80.91.229.3 (9 Apr 2012 16:45:16 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 9 Apr 2012 16:45:16 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Apr 09 18:45:15 2012 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 1SHHiN-0007GE-82 for ged-emacs-devel@m.gmane.org; Mon, 09 Apr 2012 18:45:15 +0200 Original-Received: from localhost ([::1]:57902 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SHHiM-0005uI-Mr for ged-emacs-devel@m.gmane.org; Mon, 09 Apr 2012 12:45:14 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:43315) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SHHiJ-0005u0-G7 for emacs-devel@gnu.org; Mon, 09 Apr 2012 12:45:12 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SHHiH-0007O0-LX for emacs-devel@gnu.org; Mon, 09 Apr 2012 12:45:11 -0400 Original-Received: from mail-gx0-f169.google.com ([209.85.161.169]:50885) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SHHiE-0007J8-8o; Mon, 09 Apr 2012 12:45:06 -0400 Original-Received: by ggeq1 with SMTP id q1so2264051gge.0 for ; Mon, 09 Apr 2012 09:45:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=HhQc2zuMOZvrfgdyzEhu1mH6up9EY6ZP1ThE9Ez7Omc=; b=OwDyghhtBaMfvPO52Wmte0z4eZV2/q8ChkdcR1zRyIp8cV4n7qfBdt8nWZPfc15zCO kdkpSVrTMmXPdr6QvN7CLI01VyZ4WvHK5eMSvBi3sLGQvGIw6xTILADmyDmycH9vrDc9 ak5HlUsm4K7Vgqewd2zVnzZ3+pb2ftPKT9uef/g/zGVzvTk3XWdPVZ57eRo1YSJU1L8A tfSsR2CHhNRvMQo0oR5t5D//UJ0aWTtvGY7XRIAUIKHM1JOqxmwXjaV9x64Er7IvFLC5 yehTXL3sckiaZo7uf7jQnYtlWVN96XPZ/MnfCsk106dUGjDRkqPF80F/u3bYr3a081Vy 3Dxg== Original-Received: by 10.236.197.66 with SMTP id s42mr6518867yhn.69.1333989903618; Mon, 09 Apr 2012 09:45:03 -0700 (PDT) Original-Received: by 10.147.168.13 with HTTP; Mon, 9 Apr 2012 09:45:03 -0700 (PDT) In-Reply-To: X-Google-Sender-Auth: WA08iONEg5o17_XHY91a1K_kCZ8 X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 209.85.161.169 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:149521 Archived-At: --20cf303f6d6856d50204bd41baf5 Content-Type: text/plain; charset=ISO-8859-1 cl-clean sounds a bit like a development stage in a project (alpha, beta, clean...) -- might be confusing as a permanent package name? other than that, sounds good. other possibilities: cl2 cl-new cl-compat cl-ext cl-exts cl-extensions btw, the name prefix will stay as cl- , as in cl-remove-if, whatever the 'require symbol, correct? also, should the names be changed everywhere in the CL package manual, or just add a separate section saying that the following names should really be prefixed? also: should i also add cl- aliases for macro names in CL, for uniformity? eg proclaim is a function while declaim is a macro, but should the user have to keep that in mind or just use cl-proclaim and cl-declaim and have it work? On Mon, Apr 9, 2012 at 12:24 PM, Stefan Monnier wrote: > > Maybe cl-runtime, or cl-rt? > > I'd rather not insist on the "runtime" side. It will just be the new > canonical name of "cl". We can't use "cl" because too many package > presume an implementation of "cl" which is not namespace clean, whereas > the new "cl" will be namespace-clean. > > Maybe 'cl-clean' ? > > > Stefan > > > > We need a (require 'cl-) which brings up CL but only within > >> the "cl-" namespace. I don't have a good idea for naming. `cl-defs' > >> might be OK, but I'm open to other suggestions. Maybe `cl-layer', or > >> `cl-emu', or `cl-compat'? > >> `cl-funs' is another option, indeed. > >> > --20cf303f6d6856d50204bd41baf5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable cl-clean sounds a bit like a development stage in a project (alpha, beta, c= lean...) -- might be confusing as a permanent
package name? =A0other th= an that, sounds good.

other possibilities:
cl2
cl-new
cl-compat
cl-ext
cl-exts=
cl-extensions

btw, the name prefix will= stay as cl- , as in cl-remove-if, whatever the 'require symbol, correc= t?

also, should the names be changed everywhere in the CL = package manual, or just add a separate section
saying that the fo= llowing names should really be prefixed?

also: sho= uld i also add cl- aliases for macro names in CL, for uniformity? =A0eg pro= claim is a function while declaim
is a macro, but should the user have to keep that in mind or just use = cl-proclaim and cl-declaim and have it work?
--20cf303f6d6856d50204bd41baf5--