unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: David O'Toole <dto@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: un-deprecating CL
Date: Sun, 16 Sep 2007 23:58:52 -0400	[thread overview]
Message-ID: <E1IX7l6-0007k5-DB@fencepost.gnu.org> (raw)
In-Reply-To: <m3wsuqe0ka.fsf@gnu.org> (message from David O'Toole on Sun, 16 Sep 2007 17:56:53 -0400)

    > One possible alternative is to define these functions with a cl-
    > prefix, and for callers to use that prefix.  That gets rid of the
    > namespace issue.  And if we think of them as internal parts of
    > some Lisp package, they would not have to be in the Lisp Manual.

    Would it be possible to use compiler macros so that existing programs
    could continue to use these functions' un-prefixed names at compile
    time?

That would be possible, but it seems like a bad idea -- it would
confuse people reading the program.  Writing the calls with `cl-'
would be a clearer practice.

    That would be helpful but it would still prevent many programs from
    being contributed.

"Prevent" is too strong a word.  These programs would need some change
in order to be installed in Emacs.

Adding `cl-' in front of certain function names is a pretty easy
change to make; we could add a command like query-replace to do it
semiautomatically.

  reply	other threads:[~2007-09-17  3:58 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-14 16:42 un-deprecating CL Joe Wells
2007-09-14 17:32 ` David O'Toole
2007-09-15  2:08   ` Richard Stallman
2007-09-14 19:21 ` Karl Fogel
2007-09-15  8:00   ` Eli Zaretskii
2007-09-15 18:06     ` Richard Stallman
2007-09-15 18:14       ` Leo
2007-09-15 21:56         ` Eli Zaretskii
2007-09-15 19:02       ` Joe Wells
2007-09-15 19:14         ` martin rudalics
2007-09-17  0:21           ` Richard Stallman
2007-09-17  5:58             ` martin rudalics
2007-09-15 19:41         ` T. V. Raman
2007-09-17  0:21           ` Richard Stallman
2007-09-18 14:59             ` Johan Bockgård
2007-09-19  3:18               ` Richard Stallman
2007-09-19  3:43                 ` Stefan Monnier
2007-09-20 16:34                   ` Richard Stallman
2007-09-20 18:37                     ` Stefan Monnier
2007-09-20 19:15                       ` Johan Bockgård
2007-09-21 22:32                       ` Richard Stallman
2007-09-19  3:18               ` Richard Stallman
2007-09-15 19:52         ` T. V. Raman
2007-09-17  0:21           ` Richard Stallman
2007-09-17  0:21         ` Richard Stallman
2007-09-17  2:25           ` Joe Wells
2007-09-17 15:53             ` Richard Stallman
2007-09-17 17:05               ` David O'Toole
2007-09-18  3:29                 ` Richard Stallman
2007-09-18  7:33                   ` Lennart Borgman (gmail)
2007-09-18 19:34                     ` Richard Stallman
2007-09-18 23:48                       ` David O'Toole
2007-09-19 15:49                         ` Richard Stallman
2007-09-19 21:17                           ` David O'Toole
2007-09-17  4:35           ` David O'Toole
2007-09-17 22:25             ` Richard Stallman
2007-09-17 22:25             ` Richard Stallman
2007-09-18 14:43             ` Johan Bockgård
2007-09-16 21:56       ` David O'Toole
2007-09-17  3:58         ` Richard Stallman [this message]
2007-09-16 21:46     ` David O'Toole
2007-09-16 22:22       ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1IX7l6-0007k5-DB@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=dto@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).