From: Ilya Shlyakhter <ilya_shl@alum.mit.edu>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: CL package suggestion
Date: Mon, 9 Apr 2012 12:54:11 -0400 [thread overview]
Message-ID: <CACfYvRbEycwhPK3fQoQ6SBy2eOAkgnuKa3p=C-dUQXt7TOjvLw@mail.gmail.com> (raw)
In-Reply-To: <CACfYvRYHHk6Soic_sOTy2MYccG7ze9G_QwZypcagbX=K6VEEqw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1676 bytes --]
p.s. cl-compat is taken (though obsolete), so that's not an option.
On Mon, Apr 9, 2012 at 12:45 PM, Ilya Shlyakhter <ilya_shl@alum.mit.edu>wrote:
> 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 <monnier@iro.umontreal.ca>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-<something>) 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.
>> >>
>>
>
>
[-- Attachment #2: Type: text/html, Size: 2634 bytes --]
next prev parent reply other threads:[~2012-04-09 16:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 16:52 CL package suggestion Ilya Shlyakhter
2012-04-03 16:58 ` Glenn Morris
2012-04-03 17:00 ` Glenn Morris
2012-04-03 17:09 ` Ilya Shlyakhter
2012-04-03 18:58 ` Stefan Monnier
2012-04-04 1:56 ` Ilya Shlyakhter
2012-04-04 13:06 ` Stefan Monnier
2012-04-09 1:39 ` Ilya Shlyakhter
2012-04-09 1:41 ` Ilya Shlyakhter
2012-04-09 4:54 ` Ilya Shlyakhter
2012-04-09 13:28 ` Stefan Monnier
2012-04-09 14:38 ` Ilya Shlyakhter
2012-04-09 16:24 ` Stefan Monnier
2012-04-09 16:45 ` Ilya Shlyakhter
2012-04-09 16:54 ` Ilya Shlyakhter [this message]
2012-04-10 12:51 ` Stefan Monnier
2012-04-11 4:18 ` Richard Stallman
2012-04-11 14:12 ` Ilya Shlyakhter
2012-04-11 14:32 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACfYvRbEycwhPK3fQoQ6SBy2eOAkgnuKa3p=C-dUQXt7TOjvLw@mail.gmail.com' \
--to=ilya_shl@alum.mit.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.