all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David O'Toole <dto@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: un-deprecating CL
Date: Fri, 14 Sep 2007 13:32:21 -0400	[thread overview]
Message-ID: <m3642d9mqi.fsf@gnu.org> (raw)
In-Reply-To: 864phxjj03.fsf@macs.hw.ac.uk


Hello fellow Emacsians,

I would like to point out that my comments were made informally on my
blog, and that the notes at the end about "radical action" and such
are intended to be tongue-in-cheek.

I had planned to revise it further before bothering the emacs-devel
list with the issue; in particular I would have made it sound less
like a rant :-) but also would have tried to bolster my arguments a
little and see if there were other workarounds. For example, i saw the
following in the Emacs TODO file:

> ** Implement popular parts of the rest of the CL functions as compiler
>    macros in cl-macs.

and it occurred to me that I might be able to help.

My point in this is not to complain, but to see if I can help improve
things by helping other developers write their Emacs Lisp programs
more easily.  (I have found it easier to read and write my own
programs since learning the CL package, although it took a significant
investment in time to learn it.)

Joe Wells <jbw@macs.hw.ac.uk> writes:

> I just saw this wonderful essay by Dave O'Toole entitled
>
>   "(require 'cl) considered harmful" considered harmful
>
> at this URL:
>
>   http://dto.freeshell.org/blog/blog-2007-09-07-2323.html
>
> I agree completely with its reasoning.
>
> Therefore, I propose that the warnings in the manual against relying
> on CL and the byte-compiler warnings when you use a CL function should
> both be removed.
>
> I hope this suggestion is helpful.
>
> -- 
> Joe

-- 
David O'Toole 
dto@gnu.org
http://dto.freeshell.org/notebook/

  reply	other threads:[~2007-09-14 17:32 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 [this message]
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
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

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

  git send-email \
    --in-reply-to=m3642d9mqi.fsf@gnu.org \
    --to=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 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.