From: Tony Day <zygomega@gmail.com>
To: Pascal J. Bourguignon <pjb@informatimago.com>
Cc: emacs-devel@gnu.org
Subject: Re: is requiring cl bad?
Date: Tue, 18 Dec 2012 12:58:59 +1100 [thread overview]
Message-ID: <CE5122BC-8748-45BF-AAA3-9785EBFC00EB@gmail.com> (raw)
In-Reply-To: <87txrkfqcl.fsf@kuiper.lan.informatimago.com>
On 18 Dec 2012, at 06:09, Pascal J. Bourguignon <pjb@informatimago.com> wrote:
>>
>> 24.3 finally provides an alternative: `cl-lib' which offers the
>> same functionality but in a namespace-clean way (i.e. using a "cl-"
>> prefix everywhere).
>
> This is a silly solution.
> The right solution is to implement a package system.
FWIW, I had a lot of trouble with cl when I started learning elisp. Did I have to learn the entire cl way of doing things to be proficient in emacs coding? Why was it 'special' in comparison to any other library/package but not so special as to be fully part of elisp? In retrospect, treating cl functionality as non-core helped accelerate my learning phase and better understand how to write useful emacs code.
cl-lib is an awesome library that I hope to understand and use properly (one day). That it was partially tolerated in the past is one of those difficult to reverse mistakes and I think the solution is quite respectful and graceful considering.
Tony
next prev parent reply other threads:[~2012-12-18 1:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-16 9:29 is requiring cl bad? Ivan Kanis
2012-12-16 10:14 ` Xue Fuqiao
2012-12-16 10:26 ` Pascal J. Bourguignon
2012-12-16 10:36 ` Xue Fuqiao
2012-12-16 11:00 ` Ivan Kanis
2012-12-16 17:06 ` Stefan Monnier
2012-12-17 19:09 ` Pascal J. Bourguignon
2012-12-18 1:58 ` Tony Day [this message]
2012-12-20 4:46 ` David De La Harpe Golden
2012-12-20 5:20 ` Ivan Kanis
2012-12-20 9:16 ` Helmut Eller
2012-12-21 7:05 ` David De La Harpe Golden
2012-12-21 9:24 ` Helmut Eller
2012-12-17 20:58 ` Ivan Kanis
2012-12-18 4:04 ` 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
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=CE5122BC-8748-45BF-AAA3-9785EBFC00EB@gmail.com \
--to=zygomega@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=pjb@informatimago.com \
/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).